From: Sebastian Moeller <moeller0@gmx.de>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] TSO sizing and FQ scheduler
Date: Tue, 5 Nov 2013 14:39:28 +0100 [thread overview]
Message-ID: <9121FF2E-E01C-4FDD-A374-F1CB4EED5FAB@gmx.de> (raw)
In-Reply-To: <CAMZR1YDU96DE7gYneu-766Vt30kXLWtVSwL1ifF0+X7ZmzADZA@mail.gmail.com>
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).
>
> 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.
Best
Sebastian
>
> Best regards,
> Maciej
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2013-11-05 13:39 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 [this message]
2013-11-17 22:25 ` Dave Taht
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=9121FF2E-E01C-4FDD-A374-F1CB4EED5FAB@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=maciej@soltysiak.com \
/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