From: Tom Gundersen <teg@jklm.no>
To: Michal Schmidt <mschmidt@redhat.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] SQM in mainline openwrt, fq_codel considered for fedora default
Date: Tue, 21 Oct 2014 20:06:48 +0200 [thread overview]
Message-ID: <CAG-2HqWbnT6bMimnA8BC4=D_M_XFzH=qQ-SUqAWEzNP68a5vRA@mail.gmail.com> (raw)
In-Reply-To: <54469B96.50204@redhat.com>
On Tue, Oct 21, 2014 at 7:44 PM, Michal Schmidt <mschmidt@redhat.com> wrote:
> On 10/21/2014 07:24 PM, Tom Gundersen wrote:
>> I have now subscribed to cerowrt-devel (long overdue), and I would
>> very much appreciate any comments you guys may have on our networking
>> work in systemd. In particular, if there are any more tweaks like
>> making fq_codel the deafult, which would be the reasonable choice for
>> 95% of users (most of whom don't know about these things and would
>> otherwise never touch them), we are very open to suggestions.
>
> An idea: Can networkd configure interfaces' txqueuelen?
> (Though with BQL and codel maybe it's not that important anymore.)
Hm, the way I read the docs, figuring out the "good" values is not
that straight-forward, and doing this will anyway be obsolete soon, so
not sure we should be setting anything by default. However, we
probably should make it much simpler to configure. We could add
support for both ringbuffer and quelength sizes to our link files [0],
so admins colud implement the bufferbloat recommendations by doing
something like:
----8<------
/etc/systemd/network/00-wlan.link
[Match]
Type=wlan
[Link]
TransmitRingBuffer=4
TransmitQueueLength=16
----8<------
(suggestions welcome for the naming of the variables and also for man
page sections).
These settings would then be applied by udev to any udev interface as
it appears (and before libudev notifies applications about its
existence).
Does something like this make sense?
Cheers,
Tom
[0]: <http://www.freedesktop.org/software/systemd/man/systemd.link.html>
[1]: <http://www.bufferbloat.net/projects/bloat/wiki/Linux_Tips>
next prev parent reply other threads:[~2014-10-21 18:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 18:56 Dave Taht
2014-10-17 19:30 ` Valdis.Kletnieks
2014-10-20 17:03 ` Dave Taht
2014-10-20 17:41 ` Valdis.Kletnieks
2014-10-21 14:50 ` Michal Schmidt
2014-10-21 16:27 ` Valdis.Kletnieks
2014-10-21 16:57 ` Dave Taht
2014-10-21 17:05 ` Michal Schmidt
2014-10-21 17:24 ` Tom Gundersen
2014-10-21 17:44 ` Michal Schmidt
2014-10-21 17:52 ` David Personette
2014-10-21 18:00 ` Michal Schmidt
2014-10-21 18:06 ` Tom Gundersen [this message]
2014-10-21 19:21 ` Dave Taht
2014-10-21 19:51 ` Dave Taht
2014-10-21 20:59 ` Dave Taht
2014-12-04 16:09 ` Tom Gundersen
2014-12-04 18:24 ` Dave Taht
2014-10-21 23:18 ` Toke Høiland-Jørgensen
2014-12-04 15:05 ` Tom Gundersen
2014-12-04 15:08 ` Toke Høiland-Jørgensen
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='CAG-2HqWbnT6bMimnA8BC4=D_M_XFzH=qQ-SUqAWEzNP68a5vRA@mail.gmail.com' \
--to=teg@jklm.no \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=mschmidt@redhat.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