From: Alan Goodman <notifications@yescomputersolutions.com>
To: lartc@vger.kernel.org
Subject: Re: SFQ + speed caps
Date: Wed, 06 Aug 2014 21:21:33 +0000 [thread overview]
Message-ID: <53E29C5D.1090700@yescomputersolutions.com> (raw)
In-Reply-To: <53E1EE68.8030503@gmail.com>
> .. but this way I am getting the capped pc out of the SFQ round robin
> allowing it to monopolize the line up to its hard limit and in excess
> of what is currently fair. If, for example, the capped pc speed is set
> at 40% of the line speed and there are 5 active pcs on the lan then
> the capped pc will managed to steal more than it's fair share of the
> line. It could manage to go all the way up to 40% instead of 20%.
>
> It appears that HTB must be placed on top of SFQ for this to work:
>
> interface
> |
> +--- SFQ
> |
> +---- HTB --- class 1 (capped pc)
> |
> +----- class 2 (everything else)
>
> Only problem is, you can't attach a qdisc on top of another qdisc. You
> can only attach a qdisc on top of a class and SFQ is a classless qdisc.
I believe that this is correct. You cant feed out of sfq into any
classfull qdisc. Your simple SFQ based fairness will also very probably
break badly if someone sends or receives small packets too... The
person sending the larger packets will get a much larger share than the
person sending smaller packets...
Using htb you could have each user hitting a separate class, each with a
RATE and a common CEIL so that they can all burst if the line isnt
contended... Then feed each of those that info BFIFO with limit set
just over 2x MTU sized packets (if the connection is relatively slow).
Alternatively if your O/S has it check out fq_codel.
Alan
next prev parent reply other threads:[~2014-08-06 21:21 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 [this message]
2014-08-06 22:41 ` Dimitris Kotsonis
2014-08-07 14:41 ` Dimitris Kotsonis
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=53E29C5D.1090700@yescomputersolutions.com \
--to=notifications@yescomputersolutions.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.