Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: EGAL Vincent <egal@ipanematech.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] questions on CBQ
Date: Tue, 10 Dec 2002 13:57:15 +0000	[thread overview]
Message-ID: <marc-lartc-103952883125130@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103945392624161@msgid-missing>

Stef Coene wrote:

>On Monday 09 December 2002 18:11, James Ma wrote:
>  
>
>>Hi, All,
>>
>>When I use CBQ, what should I put for "avpkt"? I saw all the examples using
>>1000, but if I have a lot of voice packets which are very small, will
>>"avpkt 1000" cause any problem? 
>>    
>>
>I'm not sure, but avpkt is used in internal calculations so if you have a lot 
>of small packets, a smaller value would be better.
>
avpkt is one of the parameters used to evaluate the maxidle parameter 
for a cbq class.
maxidle can be seen as the maximum credit that a class can reach when 
being underlimit for a period of time
So the higher maxidle is, the more packets in burst the class may send 
when switching  from underlimit to overlimit.

>
>  
>
>>Another thing is, does CBQ support
>>"default" as HTB does (ex: tc qdisc add dev eth0 root handle 1: htb default
>>12)? How can I put "all other traffic" into certain class?
>>    
>>
>Cbq has no default class.  You can use a u32 filter with src 0/0 as the last 
>filter statement.
>
>Stef
>
>  
>


-- 
Vincent EGAL
Email : egal@ipanematech.com


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-12-10 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 17:11 [LARTC] questions on CBQ James Ma
2002-12-09 18:00 ` Stef Coene
2002-12-10 13:57 ` EGAL Vincent [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-103952883125130@msgid-missing \
    --to=egal@ipanematech.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox