netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, dave.taht@gmail.com
Subject: Re: [PATCH net-next] net_sched: sfq: extend limits
Date: Thu, 05 Jan 2012 14:08:43 -0500 (EST)	[thread overview]
Message-ID: <20120105.140843.1291740601133961995.davem@davemloft.net> (raw)
In-Reply-To: <1325722718.2634.17.camel@edumazet-laptop>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 05 Jan 2012 01:18:38 +0100

> SFQ as implemented in Linux is very limited, with at most 127 flows
> and limit of 127 packets. [ So if 127 flows are active, we have one
> packet per flow ]
> 
> This patch brings to SFQ following features to cope with modern needs.
> 
> - Ability to specify a smaller per flow limit of inflight packets.
>     (default value being at 127 packets)
> 
> - Ability to have up to 65408 active flows (instead of 127)
> 
> - Ability to have head drops instead of tail drops
>   (to drop old packets from a flow)
> 
> Example of use : No more than 20 packets per flow, max 8000 flows, max
> 20000 packets in SFQ qdisc, hash table of 65536 slots.
> 
> tc qdisc add ... sfq \
>         flows 8000 \
>         depth 20 \
>         headdrop \
>         limit 20000 \
> 	divisor 65536
> 
> Ram usage : 
> 
> 2 bytes per hash table entry (instead of previous 1 byte/entry)
> 32 bytes per flow on 64bit arches, instead of 384 for QFQ, so much
> better cache hit ratio.
> 
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>

Applied.

      parent reply	other threads:[~2012-01-05 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05  0:18 [PATCH net-next] net_sched: sfq: extend limits Eric Dumazet
2012-01-05 18:08 ` Laurent Chavey
2012-01-05 18:22   ` Eric Dumazet
2012-01-05 19:08 ` David Miller [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=20120105.140843.1291740601133961995.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dave.taht@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --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).