All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: SFQ + speed caps
Date: Thu, 07 Aug 2014 22:14:38 +0000	[thread overview]
Message-ID: <53E3FA4E.1080709@gmail.com> (raw)
In-Reply-To: <53E1EE68.8030503@gmail.com>

Dimitris Kotsonis wrote:
>
>>
>> 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.
>>
> I could do that but for a class C lan I would have to create 256
> seperate classes and 256 separate filters. Each for every ip. Whereas
> in SFQ you only have to specify that the hashing algorithm should
> work on the dst field & 0xFF and everything works automatically. For
> more than 256 ips things will get really clattered. Also I wonder if
> speed is an issue here with so many rules.

I don't think 256 is that much depending on h/w of course, You can hash
filters and using htb would let you do more eg. give priority to small
packets per user.

If you really want sfq, then to limit one user and go onto one sfq I
think you would need to look into ifb so you could double process some
packets.

      parent reply	other threads:[~2014-08-07 22:14 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
2014-08-07 16:56 ` Dimitris Kotsonis
2014-08-07 22:14 ` Andy Furniss [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=53E3FA4E.1080709@gmail.com \
    --to=adf.lists@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.