General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Michael Welzl <michawe@ifi.uio.no>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
	bloat@lists.bufferbloat.net,
	BBR Development <bbr-dev@googlegroups.com>
Subject: Re: [Bloat] Trying to *really* understand Linux pacing
Date: Mon, 19 Feb 2024 09:02:24 -0500	[thread overview]
Message-ID: <CAA93jw6ycxsz4XvkE3F=MnLvFrBW66buNpCHOwPEn40x5JkpJw@mail.gmail.com> (raw)
In-Reply-To: <DE7C9FBC-8E67-408B-A1A3-3FE04FC71F51@ifi.uio.no>

also your investigation showed me a probably bug in cake's
gso-splitting. thanks!

However, after capturing the how as you just have, deeper
understanding the effects on the network itself of this stuff would be
great.

On Mon, Feb 19, 2024 at 8:54 AM Michael Welzl via Bloat
<bloat@lists.bufferbloat.net> wrote:
>
> Dear all,
>
> I’m now finally done updating the document, based on inputs from various folks in this round - most notably Neal, who went to great lengths to help me understand what I saw in my tests (thank you!).  Now the description should be mostly correct (I hope) and pretty complete, and it also includes TSO / GSO.
>
> Comments are still welcome if anyone sees a mistake or something:
> https://docs.google.com/document/d/1-uXnPDcVBKmg5krkG5wYBgaA2yLSFK_kZa7xGDWc7XU/edit?usp=sharing
>
> Several people have in the meanwhile told me that this is useful for the community. I’m glad to hear that!  I really only started this for myself, just to understand what’s going on. Now I believe I do… but hey, if this helps others too, this is great!   So, please feel free to forward this.
>
> Cheers,
> Michael
>
>
> On 7 Feb 2024, at 21:13, Neal Cardwell <ncardwell@google.com> wrote:
>
> Thanks, Michael, for the nice doc! This is really nice for the Linux networking community to have. I posted a few comments.
>
> thanks,
> neal
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat



-- 
40 years of net history, a couple songs:
https://www.youtube.com/watch?v=D9RGX6QFm5E
Dave Täht CSO, LibreQos

  reply	other threads:[~2024-02-19 14:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 11:56 Michael Welzl
2024-02-07 12:05 ` Dave Taht
2024-02-07 12:08   ` Michael Welzl
2024-02-07 12:20     ` Dave Taht
2024-02-07 20:13       ` Neal Cardwell
2024-02-19 13:54         ` Michael Welzl
2024-02-19 14:02           ` Dave Taht [this message]
2024-02-07 15:03   ` Stephen Hemminger

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='CAA93jw6ycxsz4XvkE3F=MnLvFrBW66buNpCHOwPEn40x5JkpJw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bbr-dev@googlegroups.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=michawe@ifi.uio.no \
    --cc=netdev@vger.kernel.org \
    /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