Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jonathan Thibault <jonathan@navigue.com>
Cc: Patrick McHardy <kaber@trash.net>, netdev@vger.kernel.org
Subject: Re: large divisor for flow classifier
Date: Fri, 15 Oct 2010 22:01:45 +0200	[thread overview]
Message-ID: <1287172905.2799.8.camel@edumazet-laptop> (raw)
In-Reply-To: <4CB899F7.0@navigue.com>

Le vendredi 15 octobre 2010 à 14:14 -0400, Jonathan Thibault a écrit :
> 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
> 

SFQ is limited to a 1024 divisor

You might try following patch :

(8192 is the smallest power of two greater than 6144)

sizeof(struct sfq_sched_data) becomes 0x2ccc instead of 0x10cc

keep in mind hash distribution is not perfect.

What would be the real rate ?


diff --git a/net/sched/sch_sfq.c b/net/sched/sch_sfq.c
index 3cf478d..c4a53d6 100644
--- a/net/sched/sch_sfq.c
+++ b/net/sched/sch_sfq.c
@@ -77,7 +77,7 @@
 	It is easy to increase these values, but not in flight.  */
 
 #define SFQ_DEPTH		128
-#define SFQ_HASH_DIVISOR	1024
+#define SFQ_HASH_DIVISOR	8192
 
 /* This type should contain at least SFQ_DEPTH*2 values */
 typedef unsigned char sfq_index;



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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15 18:14 large divisor for flow classifier Jonathan Thibault
2010-10-15 20:01 ` Eric Dumazet [this message]
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=1287172905.2799.8.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=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