Detail report for faq/pf/it/queueing.html, v 1.33:


[en]
409s 411p

name of one of the queues defined in the <tt>altq on</tt> directive's
<tt><i>queue_list</i></tt>. For <tt>cbq</tt> it can also match the name
of a queue in a previous <tt>queue</tt> directive's
<tt><i>queue_list</i></tt>. Queue names must be no longer than 15 characters.
<li><tt><i>interface</i></tt> - the network interface that the queue is
410s 412p
<tt><i>queue_list</i></tt>. For <tt>cbq</tt> it can also match the name
of a queue in a previous <tt>queue</tt> directive's
<tt><i>queue_list</i></tt>. Queue names must be no longer than 15 characters.
<li><tt><i>interface</i></tt> - the network interface that the queue is
valid on. This value is optional, and when not specified, will make

[it]
no corresponding hunk in [it]


[en]
no corresponding hunk in [en]

[it]
452s 454p

conservare nella coda. Quando non specificato viene utilizzato il valore
di default pari a 50.
<li><tt><i>scheduler</i></tt> - lo scheduler utilizzato, <TT>cbq</TT>
o <tt>priq</tt>. Deve essere lo stesso della coda root.
<li><tt><I>sched_options</i></tt> - ulteriori opzioni possono essere
452s 454p
conservare nella coda. Quando non specificato viene utilizzato il valore
di default pari a 50.
<li><tt><i>scheduler</i></tt> - lo scheduler utilizzato, <TT>cbq</TT>
o <tt>priq</tt>. Deve essere lo stesso della coda root.
<li><tt><I>sched_options</i></tt> - ulteriori opzioni possono essere

[en]
429s 431p

When not specified, a default of 50 is used.
<li><tt><i>scheduler</i></tt> - the scheduler being used, either <tt>cbq</tt>
or <tt>priq</tt>. Must be the same as the root queue.
<li><tt><i>sched_options</i></tt> - further options may be passed to the scheduler
to control its behavior:
429s 431p
When not specified, a default of 50 is used.
<li><tt><i>scheduler</i></tt> - the scheduler being used, either <tt>cbq</tt>
or <tt>priq</tt>. Must be the same as the root queue.
<li><tt><i>sched_options</i></tt> - further options may be passed to the scheduler
to control its behavior:

[it]
no corresponding hunk in [it]


[en]
430s 432p

<li><tt><i>scheduler</i></tt> - the scheduler being used, either <tt>cbq</tt>
or <tt>priq</tt>. Must be the same as the root queue.
<li><tt><i>sched_options</i></tt> - further options may be passed to the scheduler
to control its behavior:
<ul>

[it]
454s 456p

<li><tt><i>scheduler</i></tt> - lo scheduler utilizzato, <TT>cbq</TT>
o <tt>priq</tt>. Deve essere lo stesso della coda root.
<li><tt><I>sched_options</i></tt> - ulteriori opzioni possono essere
passate allo scheduler per controllare il suo comportamento:
<ul>

[en]
526s 528p


<p>
Normally only one queue name is given with the <tt>queue</tt> keyword,
but if a second name is specified that queue will be used for packets
with a <a href="http://www.rfc-editor.org/rfc/rfc791.txt">Type of
526s 528p

<p>
Normally only one queue name is given with the <tt>queue</tt> keyword,
but if a second name is specified that queue will be used for packets
with a <a href="http://www.rfc-editor.org/rfc/rfc791.txt">Type of

[it]
550s 552p


<p>
Normalmente con la keyword <TT>queue</TT> si definisce un solo nome di
coda, se viene specificato un secondo nome quella coda
sarà usata per pacchetti con un
550s 552p

<p>
Normalmente con la keyword <TT>queue</TT> si definisce un solo nome di
coda, se viene specificato un secondo nome quella coda
sarà usata per pacchetti con un

[en]
546s 548p

because the <tt>ssh_login</tt> queue has a higher priority.

<p>
Assigning TCP ACK packets to a higher priority queue is useful on
asymmetric connections, that is, connections that have different upload

[it]
no corresponding hunk in [it]


[en]
no corresponding hunk in [en]

[it]
574s 576p

<tt>ssh_bulk</tt>.

<p>
Assegnare i pacchetti TCP ACK ad una coda a più elevata priorità è utile
nelle connessioni asimmetriche, cioè connessioni a differenti bande in