From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Rosen Penev <rosenp@gmail.com>
Cc: dave.taht@gmail.com, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Flow offload's impact on bufferbloat
Date: Fri, 17 Aug 2018 09:28:06 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1808170924460.19688@uplift.swm.pp.se> (raw)
In-Reply-To: <CAKxU2N-GZp4e4FO675fM2oL00shr154cYwggaVK58nJ9EbAHxA@mail.gmail.com>
On Fri, 10 Aug 2018, Rosen Penev wrote:
> My question is not really how to fix it. I already know that. I just
> got the feeling that bypassing parts of the linux network stack would
> result in less buffering.
On the OpenWrt configuration page for the "software flow offload":
"Experimental feature. Not fully compatible with QoS/SQM."
I don't know exactly what it does, it reduces amount of CPU cycles needed
to forward packets in an already established flow it seems, but I'd
imagine that it might very well bypass some of the scheduling code which
could explain what you're seeing. So you might get faster forwarding but
less AQM.
So if your device isn't fast enough to keep up with your total Internet
access speed, then this might be a good thing. If your device is faster
than what's needed, then you'd better spend the cycles on getting good AQM
instead of freeing up more CPU that isn't used for anything anyway.
--
Mikael Abrahamsson email: swmike@swm.pp.se
prev parent reply other threads:[~2018-08-17 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 23:12 Rosen Penev
2018-08-10 23:15 ` Jonathan Morton
2018-08-10 23:18 ` Dave Taht
2018-08-10 23:35 ` Rosen Penev
2018-08-10 23:55 ` Jonathan Morton
2018-08-17 7:28 ` Mikael Abrahamsson [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1808170924460.19688@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=rosenp@gmail.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