From: Jonathan Thibault <jonathan@navigue.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Patrick McHardy <kaber@trash.net>,
netdev@vger.kernel.org
Subject: Re: large divisor for flow classifier
Date: Fri, 15 Oct 2010 19:58:18 -0400 [thread overview]
Message-ID: <4CB8EA9A.9020604@navigue.com> (raw)
In-Reply-To: <4CB8C341.40000@gmail.com>
I will certainly look into that.
Jonathan
On 15/10/10 05:10 PM, Jarek Poplawski wrote:
> Eric Dumazet wrote:
>
> Because of low SFQ_DEPTH, which limits its queue to 127 packets,
> SFQ isn't suitable for serving so many users. There is sch_drr as
> a replacement, alas more complex and undocumented, but google should
> help you enough.
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=13d2a1d2b032de08d7dcab6a1edcd47802681f96
>
> Jarek P.
next prev parent reply other threads:[~2010-10-15 23:58 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
2010-10-15 21:10 ` Jarek Poplawski
2010-10-15 21:45 ` Jarek Poplawski
2010-10-15 23:58 ` Jonathan Thibault [this message]
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=4CB8EA9A.9020604@navigue.com \
--to=jonathan@navigue.com \
--cc=eric.dumazet@gmail.com \
--cc=jarkao2@gmail.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).