All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Oliver Schulze L." <oliver@samera.com.py>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What is: "Consider r2q change"
Date: Mon, 30 May 2005 17:52:40 +0000	[thread overview]
Message-ID: <429B52E8.4080005@samera.com.py> (raw)
In-Reply-To: <429650AD.5050506@samera.com.py>

Hi, yes, thats right, the problem was only with leaf classes.
Thanks for clarifyind that

Oliver

m.innocenti@cineca.it wrote:

> Oliver Schulze L. ha scritto:
>
>> I'm getting this warning/error in /var/log/messages:
>> May 26 18:21:05 mail kernel: HTB: quantum of class 10010 is small. 
>> Consider r2q change.
>> Its a big deal? What should I do?
>
>
> If I understand the source, that message occours when you have a leaf 
> class whose calculated quantum (rate/r2q) is less than 1000 byte and 
> the kernel set the quantum to 1000 byte.
> I've read that the quantum should be bigger than the MTU so I don't 
> understand why the kernel don't use a minimum quantum value bigger 
> than 1500. Someone has a clue?
>
> From kernel-source-2.6.10/net/sched/sch_htb.c
> if (!hopt->quantum && cl->un.leaf.quantum < 1000) {
>    printk(KERN_WARNING "HTB: quantum of class %X is small. Consider 
> r2q change.\n", cl->classid);
>    cl->un.leaf.quantum = 1000;
>
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-05-30 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 22:41 [LARTC] What is: "Consider r2q change" Oliver Schulze L.
2005-05-27  3:26 ` gypsy
2005-05-27  6:00 ` m.innocenti
2005-05-30 16:47 ` Oliver Schulze L.
2005-05-30 17:52 ` Oliver Schulze L. [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=429B52E8.4080005@samera.com.py \
    --to=oliver@samera.com.py \
    --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.