netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Thibault <jonathan@navigue.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org
Subject: large divisor for flow classifier
Date: Fri, 15 Oct 2010 14:14:15 -0400	[thread overview]
Message-ID: <4CB899F7.0@navigue.com> (raw)

 It appears that when setting a fairly large divisor on the flow classifier for sfq, traffic stops altogether.

On my machine, anything above divisor 2200 seems to stop all traffic.  If I want to be fair between hosts (but not flows) for a large network (say 6000 hosts), I run into problems.  Obviously the rates here are quite low but this is just an example.

I also tested on a real interface with the same results.

Example that works:

tc qdisc add dev ifb0 root handle 3: htb default 10
  tc class add dev ifb0 parent 3: classid 3:1 htb rate 80kbit
    tc class add dev ifb0 parent 3:1 classid 3:10 htb rate 80kbit
      tc qdisc add dev ifb0 parent 3:10 handle 310: sfq perturb 10
      tc filter add dev ifb0 parent 3: protocol all prio 1 u32 match mark 0x000 0xf00 flowid 3:10
      tc filter add dev ifb0 parent 310: protocol all handle 0x310 flow hash keys dst divisor 1024

Example that doesn't work:

tc qdisc add dev ifb0 root handle 3: htb default 10
  tc class add dev ifb0 parent 3: classid 3:1 htb rate 80kbit
    tc class add dev ifb0 parent 3:1 classid 3:10 htb rate 80kbit
      tc qdisc add dev ifb0 parent 3:10 handle 310: sfq perturb 10
      tc filter add dev ifb0 parent 3: protocol all prio 1 u32 match mark 0x000 0xf00 flowid 3:10
      tc filter add dev ifb0 parent 310: protocol all handle 0x310 flow hash keys dst divisor 6144

Jonathan

             reply	other threads:[~2010-10-15 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15 18:14 Jonathan Thibault [this message]
2010-10-15 20:01 ` large divisor for flow classifier Eric Dumazet
2010-10-15 21:10   ` Jarek Poplawski
2010-10-15 21:45     ` Jarek Poplawski
2010-10-15 23:58     ` Jonathan Thibault
2010-10-15 23:52   ` Jonathan Thibault

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=4CB899F7.0@navigue.com \
    --to=jonathan@navigue.com \
    --cc=kaber@trash.net \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).