All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viktar Sakovich <atlantos@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB prio: global or per class ?
Date: Fri, 17 Nov 2006 13:53:04 +0000	[thread overview]
Message-ID: <06111715530400.00818@localhost> (raw)
In-Reply-To: <81c11a560611160926seb0c72ey4a6426a364274849@mail.gmail.com>

On Friday 17 November 2006 09:57, you wrote:
> Okay
>
> Which among you rightly? Who tests that ?

Me for example.

> If the the prio is global, it's strange and not very usefull and limit a
> lot the HTB scheduler.

I agree. But it's the way it works.

> Normaly if HTB respecte the diffserv, the prio are per class basis.
> Why is it global a
>
> 2006/11/16, Viktar Sakovich <atlantos@gmail.com>:
> > On Thursday 16 November 2006 19:26, you wrote:
> > > Hi all,
> > >
> > > Is the prio specification in the htb class global or is it on a per
> > > class basis ?
> > >
> > > A simple example:
> > >
> > > class 1:10 parent 1:
> > > class 1:100 parent 1:10 prio 3
> > >
> > > class 1:200 parent 1:10 prio 7
> > > class 1:201 parent 1:200 prio 1
> > > class 1:202 parent 1:200 prio 2
> > >
> > > Which class will get excessive bandwidth first? 100 or 201/202 ?
> >
> > Prio specification in the htb class is global. In this example 201/202
> > will
> > get all bandwidth.

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2006-11-17 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 17:26 [LARTC] HTB prio: global or per class ? doudouyam
2006-11-17 11:19 ` Ales Klok
2006-11-17 13:53 ` Viktar Sakovich [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=06111715530400.00818@localhost \
    --to=atlantos@gmail.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 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.