From: Patrick McHardy <kaber@trash•net>
To: hadi@cyberus•ca
Cc: netdev@vger•kernel.org
Subject: Re: [RFC NET_SCHED 00/02]: Flexible SFQ flow classification
Date: Wed, 30 May 2007 18:55:15 +0200 [thread overview]
Message-ID: <465DAC73.6070507@trash.net> (raw)
In-Reply-To: <1180542897.4109.81.camel@localhost>
jamal wrote:
> On Wed, 2007-30-05 at 18:23 +0200, Patrick McHardy wrote:
>
>>My classifier seperates them entirely. The only thing it keeps
>>in SFQ is the old classifier for compatibility, besides that its
>>exactly what you say. It should be easily possible to remove it
>>entirely and use my classifier in a compatible configuration
>>automatically.
>>
>
>
> If you removed it entirely (and had it as a separate classifier) IMO
> that would be a better approach. Then what you have is a pure FQ qdisc.
> In which case, you leave alone SFQ and have a new qdisc.
I could do that, but I'm perfectly happy with the qdisc part of SFQ.
Without the classifier SFQ is of course simply a FQ qdisc, all it
cares about is serving queues equally.
next prev parent reply other threads:[~2007-05-30 16:56 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
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 [this message]
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=465DAC73.6070507@trash.net \
--to=kaber@trash$(echo .)net \
--cc=hadi@cyberus$(echo .)ca \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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