From: Patrick McHardy <kaber@trash.net>
To: Corey Hickey <bugfood-ml@fatooh.org>
Cc: lartc <lartc@mailman.ds9a.nl>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [LARTC] ESFQ: request for user input
Date: Mon, 25 Jun 2007 01:40:54 +0200 [thread overview]
Message-ID: <467F0106.1070103@trash.net> (raw)
In-Reply-To: <467EF9B6.3040801@fatooh.org>
Corey Hickey wrote:
> Patrick McHardy wrote:
>>>
>>> Should ESFQ be merged into SFQ or remain as a separate qdisc?
>>>
>> I've CCed netdev. I think merging parts of ESFQ (dynamic depth and
>> flow number) would make a lot of sense, but I'm intending to submit
>> an alternative to the ESFQ hashing scheme for 2.6.23:
>>
>> http://www.mail-archive.com/netdev@vger.kernel.org/msg39156.html
>>
>
> Nice. I wasn't aware of that. Your patch looks like it supersedes ESFQ's
> hashing, so, if it gets applied, that already removes a large chunk of
> the differences between SFQ and ESFQ.
>
> If I don't hear any opposition, then I'll keep an eye out for when your
> patch gets accepted (assuming it does) and then submit patch(es) porting
> the rest of ESFQ's features to SFQ.
>
I think it would be best if you would start posting patches
to add the missing features (without the hash changes) to SFQ,
if you're quick this may already go in during the 2.6.23 merge
window. My changes are mostly independant of yours, if there
are any clashes the one who goes last will just have to rediff
their patches :)
Since you need to pass additional parameters to SFQ for your
changes, have a look at my rtnetlink compat attribute patch:
http://article.gmane.org/gmane.linux.network/64851
next prev parent reply other threads:[~2007-06-24 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <467ECB0C.6020105@fatooh.org>
2007-06-24 21:12 ` [LARTC] ESFQ: request for user input Patrick McHardy
2007-06-24 23:09 ` Corey Hickey
2007-06-24 23:40 ` Patrick McHardy [this message]
2007-06-24 23:45 ` [LARTC] " Corey Hickey
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=467F0106.1070103@trash.net \
--to=kaber@trash.net \
--cc=bugfood-ml@fatooh.org \
--cc=lartc@mailman.ds9a.nl \
--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).