From: Jonathan Morton <chromatix99@gmail.com>
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: Sat, 11 Aug 2018 02:55:49 +0300 [thread overview]
Message-ID: <616C8979-4722-446E-B266-CE8CE2C704C7@gmail.com> (raw)
In-Reply-To: <CAKxU2N-GZp4e4FO675fM2oL00shr154cYwggaVK58nJ9EbAHxA@mail.gmail.com>
> On 11 Aug, 2018, at 2:35 am, Rosen Penev <rosenp@gmail.com> wrote:
>
> I just got the feeling that bypassing parts of the linux network stack would
> result in less buffering.
That buffering is not happening in the linux network stack. It's happening in the hardware, both in your modem (upload) and in the ISP's equipment (download) because those are the parts which meet the bottleneck link.
When making measurements, be sure of what you're measuring.
- Jonathan Morton
next prev parent reply other threads:[~2018-08-10 23:55 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 [this message]
2018-08-17 7:28 ` Mikael Abrahamsson
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=616C8979-4722-446E-B266-CE8CE2C704C7@gmail.com \
--to=chromatix99@gmail.com \
--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