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>, devik@cdi.cz, netdev@vger.kernel.org
Subject: Re: [PATCH] sch_htb.c consume the classes's tokens bellow the HTB_CAN_SEND level
Date: Tue, 3 Nov 2009 10:05:38 +0000	[thread overview]
Message-ID: <20091103100538.GC6718@ff.dom.local> (raw)
In-Reply-To: <412e6f7f0911030147k659e0079ibd1f424fef0a487f@mail.gmail.com>

On Tue, Nov 03, 2009 at 05:47:17PM +0800, Changli Gao wrote:
> On Tue, Nov 3, 2009 at 4:00 PM, Jarek Poplawski <jarkao2@gmail.com> wrote:
> >
> >> It means that a class, which sends packets
> >> in ceil rate, can also enter HTB_CAN_SEND state now and then.
> >
> > Yes, a class is entitled to send on it's own then with it's guaranteed
> > rate, without depending on borrowing.
> 
> I don't think so. The class should _NOT_ enter HTB_CAN_SEND mode when
> its data rate is higher than its rate specification. In other word, a
> class should enter HTB_CAN_SEND mode only when its data rate isn't
> higher than its rate specification. Otherwise, it will get additional
> tokens and reach a higher data rate than its ceil specification. This
> may affect other classes.

The ceil specification is controlled only by ctokens, which are always
updated, so no such risk.

Regards,
Jarek P.

  reply	other threads:[~2009-11-03 10:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  2:41 [PATCH] sch_htb.c consume the classes's tokens bellow the HTB_CAN_SEND level Changli Gao
2009-11-03  8:00 ` Jarek Poplawski
2009-11-03  9:47   ` Changli Gao
2009-11-03 10:05     ` Jarek Poplawski [this message]
2009-11-03 13:18       ` Changli Gao
2009-11-03 23:00         ` Jarek Poplawski
2009-11-04  1:53           ` Changli Gao
2009-11-04  8:28             ` Jarek Poplawski
2009-11-04  9:16               ` Changli Gao
2009-11-04 10:42                 ` Jarek Poplawski
2009-11-04 10:58                   ` Martin Devera
2009-11-04 11:30                     ` Changli Gao
2009-11-04 11:51                       ` Martin Devera
2009-11-04 11:58                       ` Martin Devera
2009-11-04 12:08                         ` Changli Gao
2009-11-04 12:15                           ` Martin Devera
2009-11-05  5:44                             ` Changli Gao
2009-11-04 11:21                   ` Changli Gao
2009-11-04 11:49                     ` Jarek Poplawski
2009-11-04 12:01                       ` Changli Gao
2009-11-04 12:11                         ` Jarek Poplawski

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=20091103100538.GC6718@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=devik@cdi.cz \
    --cc=hadi@cyberus.ca \
    --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.