From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Michal Kubeček" <mkubecek@suse.cz>,
netdev@vger.kernel.org,
"John A. Sullivan III" <jsullivan@opensourcedevel.com>
Subject: Re: [RFC] SFQ planned changes
Date: Tue, 03 Jan 2012 13:50:36 +0100 [thread overview]
Message-ID: <1325595036.2320.43.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <CAA93jw5T10PHD+YQQjy_r=LHKVbYeiWerwM0ou7HANGoenFRKw@mail.gmail.com>
Le mardi 03 janvier 2012 à 13:07 +0100, Dave Taht a écrit :
> From a 'doing science' perspective, I'd like it if it remained possible
> to continue using and benchmarking SFQ as it was, and create
> this set of ideas as a new qdisc ('efq'?)
>
> As these changes seem to require changes to userspace tc, anyway,
> and (selfishly) my patching burden is great enough...
>
> Perhaps some additional benefit could be had by losing
> full backward API compatability with sfq, as well?
No, it's completely compatable with prior version.
An old tc command, or lack of new arguments will setup the SFQ qdisc
exactly as before.
I coded the thing and am doing stress tests before submission.
next prev parent reply other threads:[~2012-01-03 12:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-01 2:30 tc filter mask for ACK packets off? John A. Sullivan III
2012-01-03 7:31 ` Michal Kubeček
2012-01-03 9:36 ` Dave Taht
2012-01-03 10:40 ` [RFC] SFQ planned changes Eric Dumazet
2012-01-03 12:07 ` Dave Taht
2012-01-03 12:50 ` Eric Dumazet [this message]
2012-01-03 16:08 ` Eric Dumazet
2012-01-03 23:57 ` Dave Taht
2012-01-04 0:14 ` Eric Dumazet
2012-01-04 7:56 ` Dave Taht
2012-01-04 8:17 ` Eric Dumazet
2012-01-03 12:18 ` tc filter mask for ACK packets off? John A. Sullivan III
2012-01-03 12:32 ` Eric Dumazet
2012-01-03 12:45 ` John A. Sullivan III
2012-01-03 13:00 ` Dave Taht
2012-01-03 17:57 ` John A. Sullivan III
2012-01-04 0:01 ` Michal Soltys
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=1325595036.2320.43.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
--to=eric.dumazet@gmail.com \
--cc=dave.taht@gmail.com \
--cc=jsullivan@opensourcedevel.com \
--cc=mkubecek@suse.cz \
--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