From: Patrick McHardy <kaber@trash.net>
To: lists@andyfurniss.entadsl.com
Cc: netdev@vger.kernel.org, hadi@cyberus.ca
Subject: Re: [RFC NET_SCHED 00/02]: Flexible SFQ flow classification
Date: Wed, 30 May 2007 17:32:08 +0200 [thread overview]
Message-ID: <465D98F8.9000102@trash.net> (raw)
In-Reply-To: <465D5D7A.8090200@andyfurniss.entadsl.com>
Andy Furniss wrote:
> Patrick McHardy wrote:
>
>> It currently does not support perturbation, I didn't want to move this
>> into
>> the classifier, so I need to think about a way to handle it within SFQ.
>>
>
> Cool, but isn't this going to show the same collision problems that the
> pre jhash esfq saw?
Perturbation doesn't prevent collisions, it just distributes them
(hopefully evenly). My classifier uses jhash, but that won't prevent
collisions either. Anyways, I'm going to change SFQ so perturbation
can also be used with external classifiers.
next prev parent reply other threads:[~2007-05-30 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 9:40 [RFC NET_SCHED 00/02]: Flexible SFQ flow classification Patrick McHardy
2007-05-30 9:40 ` [RFC NET_SCHED 01/02]: sch_sfq: add support for external classifiers Patrick McHardy
2007-05-30 9:40 ` [RFC NET_SCHED 02/02]: Add flow classifier Patrick McHardy
2007-05-30 11:18 ` [RFC NET_SCHED 00/02]: Flexible SFQ flow classification Andy Furniss
2007-05-30 15:32 ` Patrick McHardy [this message]
2007-05-30 16:57 ` Andy Furniss
2007-05-30 14:56 ` jamal
2007-05-30 15:27 ` Patrick McHardy
2007-05-30 16:10 ` jamal
2007-05-30 16:23 ` Patrick McHardy
2007-05-30 16:34 ` jamal
2007-05-30 16:55 ` Patrick McHardy
2007-05-30 17:02 ` jamal
2007-08-09 4:12 ` Paul E. McKenney
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=465D98F8.9000102@trash.net \
--to=kaber@trash.net \
--cc=hadi@cyberus.ca \
--cc=lists@andyfurniss.entadsl.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 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.