All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tim Carr" <tcarr@rim.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Anyone seen this?
Date: Fri, 01 Nov 2002 15:43:31 +0000	[thread overview]
Message-ID: <marc-lartc-103616547705557@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103609443808983@msgid-missing>

Oops, pardon me for partially answering my own questions, but let me clarify:

1. I read the bit of the FAQ on docum.org that explains the quantum stuff. Nice site Stef.  So it looks to me that in HTB3 if your quantum is less than the packet size, since it still sends the packet anyways, it's not really limiting the packets at the rate you want? (!) .. How do I actually limit something to a cold/hard 2kbytes/sec ?  If I manually set the quantum, it'll still be lower than most packet sizes, and according to what I read in the FAQ it won't actually limit it below the packet size.

2. In HTB, which is MORE important (and therefore gets more attention): a lower or higher prio? The faq leads me to believe a LOWER prio is MORE important. (Stef you could add this in b/w to the FAQ, it's not clear).

Thanks again,

tim

> -----Original Message-----
> From: Tim Carr 
> Sent: November 1, 2002 10:29 AM
> To: Stef Coene; lartc@mailman.ds9a.nl
> Subject: RE: [LARTC] Anyone seen this?
> 
> 
> > try, I can't find
> > > out what the new syntax should be. Here's the line that's failing:
> > >
> > > tc qdisc add dev eth0 root handle 1: htb default 13
> > >
> > > Any ideas how to make that work with the new version?
> 
> > You have to use the same htb version for tc and the kernel.  
> > Maybe that's the 
> > problem.
> 
> Hmm. I'm using debian's stock version of iproute2's "tc" 
> command, and i'm using the HTB that comes with kernel 
> 2.4.20pre11. Does anyone know what version of HTB that is, 
> and whether it's the newest ?
> 
> > Quantum must be greater then 1500.  You have a class with 
> > rate 2 so the 
> > quantum of that class is 2k / 10 (10 is default) = 200.  This 
> > is smaller then 
> > 1500.  Solution : ignore the warnings :) or overrule the r2q 
> 
> Ok, is it not "working" properly because my quantum is too 
> low? What kind of ill-effects will this have?
> 
> Many thanks,
> 
> tim
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> 
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-11-01 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 19:59 [LARTC] Anyone seen this? Tim Carr
2002-10-31 21:28 ` Stef Coene
2002-11-01 15:29 ` Tim Carr
2002-11-01 15:43 ` Tim Carr [this message]
2002-11-01 15:43 ` Luc Brouard
2002-11-01 16:10 ` Stef Coene
2002-11-01 16:47 ` Tim Carr
2002-11-01 17:03 ` Stef Coene

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-103616547705557@msgid-missing \
    --to=tcarr@rim.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.