All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Changli Gao <xiaosuo@gmail.com>
Cc: Jamal Hadi Salim <hadi@cyberus.ca>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, Martin Devera <martin.devera@cdi.cz>
Subject: Re: [PATCH] sch_htb: ix the deficit overflows
Date: Tue, 1 Dec 2009 08:01:51 +0000	[thread overview]
Message-ID: <20091201080151.GA6408@ff.dom.local> (raw)
In-Reply-To: <412e6f7f0911301832o53e479f0x42345065b0b1616f@mail.gmail.com>

On Tue, Dec 01, 2009 at 10:32:26AM +0800, Changli Gao wrote:
> On Mon, Nov 30, 2009 at 7:10 PM, Jarek Poplawski <jarkao2@gmail.com> wrote:
> > On Mon, Nov 30, 2009 at 12:26:33PM +0800, Changli Gao wrote:
> >
> > Users can control this with "r2q" and "quantum", and there is a hint
> > on quantum size in the user's guide.
> 
> Yes. But I think most of users will ignore it like me.

In most cases this shouldn't matter. Default r2q/quantum should be
OK for higher rates, and lower ones (< 10pps) are probably controlled
mainly by their state, so even an overflowed deficit doesn't have to
matter (unless your tests show something else ;-).

In other cases those users should see some problems or quantum
warnings, and that's when they should stop ignoring the docs.

> 
> >
> >> And
> >> if we use IMQ to shape traffic, the skb will be defragmented by
> >> conntrack, and its size will be larger than MTU.
> >
> > IMQ is a very nice thing, but it's considered broken as well, so it
> > can't be the reason for changing HTB.
> 
> I find IMQ is used by many network equipments Linux based. Why not fix
> and integrate it into official Linux?

Even I ;-) don't know exact reasons, but I believe some people here
know better.

> 
> > And this patch is very similar, except ->peek()/dequeue(). Additional
> > lookups are done instead of dequeuing the first found class, which
> > might be quite long in some cases.
> 
> If the quantum is set correctly, there isn't difference except of a
> comparison. In the other case, I think some additional CPU cycles are
> better than overflow.

No, my main point is there _is_ a difference when the quantum is set
correctly. Just these additional lookups.

> 
> >
> > It's not acceptable to me mainly because the real change done by this
> > patch is different than you describe: preventing an overflow might be
> > simple. You change the way DRR is implemented here, and even if it's
> > right, it should be written explicitly and proved with tests results.
> >
> 
> This way is used by CBQ.

HTB is different by design:
http://luxik.cdi.cz/~devik/qos/htb/manual/theory.htm

Regards,
Jarek P.

  reply	other threads:[~2009-12-01  8:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27  8:14 [PATCH] sch_htb: ix the deficit overflows Changli Gao
2009-11-28  0:04 ` Jarek Poplawski
2009-11-30  4:26   ` Changli Gao
2009-11-30 11:10     ` Jarek Poplawski
2009-12-01  2:32       ` Changli Gao
2009-12-01  8:01         ` Jarek Poplawski [this message]
2009-12-01  8:43           ` Jarek Poplawski
2009-12-01  9:18             ` Changli Gao
2009-12-01  9:39               ` Jarek Poplawski
2009-12-01 19:12             ` Jarek Poplawski
2009-12-01 19:18               ` Jarek Poplawski
2009-12-02  9:20       ` David Miller
2009-12-02 10:32         ` Jarek Poplawski
2009-12-02 11:07           ` Martin Devera

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=20091201080151.GA6408@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=martin.devera@cdi.cz \
    --cc=netdev@vger.kernel.org \
    --cc=xiaosuo@gmail.com \
    /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.