From: Dave Taht <dave.taht@bufferbloat.net>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] TSO sizing and FQ scheduler
Date: Sun, 17 Nov 2013 14:25:06 -0800 [thread overview]
Message-ID: <20131117222506.GA13816@lists.bufferbloat.net> (raw)
In-Reply-To: <9121FF2E-E01C-4FDD-A374-F1CB4EED5FAB@gmx.de>
On Tue, Nov 05, 2013 at 02:39:28PM +0100, Sebastian Moeller wrote:
> Hi Maciej,
>
>
>
> On Nov 5, 2013, at 14:22 , Maciej Soltysiak <maciej@soltysiak.com> wrote:
>
> > Hi list,
> >
> > 3.12 landed with TSO sizing and FQ scheduler. Is there significant
> > benefit of trying to port these to Cero's 3.10 ?
>
> According to Eric Dumazet, these two help for flows terminating on the device in question, not for flows just passing through the device. So unless your cerowrt router offers lots of network services it most likely will not profit from these features… Also, IIRC, we disable TSO on cerowrt by default (though TSO sizing might mean that this decision could be revisited).
>
> >
Of interest in backporting FQ is to be able to analyze its performance
on routed streams vs fq_codel. It uses a finer grained FQ, on a 4 tuple,
but does not do queue management, so I expect the results will end up looking
like SFQ or QFQ with bigger buffers - good fairness but catastrophic effects on
fat streams, and a lot more collisions.
This is a slide I didn't get to show at ietf, showing what SFQ + longest
queue drop looks like.
http://snapon.lab.bufferbloat.net/~d/results_3.12/3.12/ecn/rtt_fair_download=5500-upload=20000-noecn-sfq-target=5ms-delay=240ms-2.svg
vs fq_codel
http://snapon.lab.bufferbloat.net/~d/results_3.12/3.12/ecn/rtt_fair_download=5500-upload=20000-ecn-fq_codel-target=5ms-delay=240ms-2.svg
vs pie
http://snapon.lab.bufferbloat.net/~d/results_3.12/3.12/ecn/rtt_fair_download=5500-upload=20000-ecn-pie-target=20ms-delay=240ms-2.svg
I expect the FQ scheduler to crash a teeny router with its defaults also...
Looking at the cpu usage would be interesting too...
I'm tempted to backport it, I am! I am!
> > I'm assuming we're not going head on to 3.12 for kernel base for cero as of yet?
>
> I would hope for 3.10 to be the kernel for the forceable future, due to its promised 2 years? maintenance window.
I intend to freeze on some variant of 3.10 for quite some time, yes.
At the moment I don't really have time to backport the new stuff
to cerowrt, I am starting a new job (yea!), and just want to make cero stable
ASAP so I can ramp up on that.
>
>
> Best
> Sebastian
>
> >
> > Best regards,
> > Maciej
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
prev parent reply other threads:[~2013-11-17 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 13:22 Maciej Soltysiak
2013-11-05 13:39 ` Sebastian Moeller
2013-11-17 22:25 ` Dave Taht [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131117222506.GA13816@lists.bufferbloat.net \
--to=dave.taht@bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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