All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitris Kotsonis <dkotsonis@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: SFQ + speed caps
Date: Thu, 07 Aug 2014 14:41:27 +0000	[thread overview]
Message-ID: <53E39017.6000208@gmail.com> (raw)
In-Reply-To: <53E1EE68.8030503@gmail.com>

On 8/7/2014 3:42 PM, Remy Mudingay wrote:
> HI Dimitris,
>
> The solution is straight forward :
>
> interface
>   |
>   +---- HTB --- class 1 parent class
>          |
>          +----- HTB class 2  (everything else) 90% guaranteed/ 100% cap
>          |        |
>          |       +--- SFQ
>          |
>          +----- HTB class 3 (capped pc) 10% guaranteed/ 20% cap
>

Hi Remy,

 From what I can tell what you posted is identical to the hypothetical 
scenario that I said will not work.

Here is the problem with it. Let's say that there are 20 pcs battling 
for bandwidth in class 2. SFQ will guarantee that each will get 
approximately 1/20th of the bandwidth. The capped pc however is 
unfettered by the SFQ round robin so it can potentially consume the 
entire chunk allocated to it by HTB in class 3, which is more than 1/20. 
So the capped pc can potentially (e.g. using a large number of sockets) 
get more bandwidth than the uncapped pcs.

So what I am looking for is for a way to implement a global SFQ instead 
of one for each HTB class. For a way to place the entire HTB logic on 
top of a single SFQ.

Regards,

Dimitris


  parent reply	other threads:[~2014-08-07 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06  8:59 SFQ + speed caps Dimitris Kotsonis
2014-08-06 21:21 ` Alan Goodman
2014-08-06 22:41 ` Dimitris Kotsonis
2014-08-07 14:41 ` Dimitris Kotsonis [this message]
2014-08-07 16:56 ` Dimitris Kotsonis
2014-08-07 22:14 ` Andy Furniss

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=53E39017.6000208@gmail.com \
    --to=dkotsonis@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.