From: Eric Dumazet <eric.dumazet@gmail.com>
To: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
Cc: "Dave Taht" <dave.taht@gmail.com>,
"Michal Kubeček" <mkubecek@suse.cz>,
netdev@vger.kernel.org
Subject: Re: tc filter mask for ACK packets off?
Date: Tue, 03 Jan 2012 13:32:31 +0100 [thread overview]
Message-ID: <1325593951.2320.40.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <1325593115.7219.36.camel@denise.theartistscloset.com>
Le mardi 03 janvier 2012 à 07:18 -0500, John A. Sullivan III a écrit :
> On Tue, 2012-01-03 at 10:36 +0100, Dave Taht wrote:
> <snip>
> > I'd go into more detail, but after what I hope are the final two
> > fixes to sfq and qfq land in the net-next kernel (after some more
> > testing), I like to think I have a more valid approach than this
> > in the works, but that too will require some more development
> > and testing.
> >
> > http://www.teklibre.com/~d/bloat/pfifo_fast_vs_sfq_qfq_linear.png
> >
> <snip>
> Hmmm . . . certainly shattered my concerns about replacing pfifo_fast
> with SFQ! Thanks - John
Before you do, take the time to read the warning in sfq source :
ADVANTAGE:
- It is very cheap. Both CPU and memory requirements are minimal.
DRAWBACKS:
- "Stochastic" -> It is not 100% fair.
When hash collisions occur, several flows are considered as one.
- "Round-robin" -> It introduces larger delays than virtual clock
based schemes, and should not be used for isolating interactive
traffic from non-interactive. It means, that this scheduler
should be used as leaf of CBQ or P3, which put interactive traffic
to higher priority band.
SFQ (as a direct replacement of dev root qdisc) is fine if most of your trafic
is of same kind/priority.
next prev parent reply other threads:[~2012-01-03 12:32 UTC|newest]
Thread overview: 18+ 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
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2012-01-01 2:30 John A. Sullivan III
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=1325593951.2320.40.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