General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Neal Cardwell <ncardwell@google.com>,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	 BBR Development <bbr-dev@googlegroups.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [bbr-dev] Aggregating without bloating - hard times for tcp and wifi
Date: Wed, 23 Nov 2022 12:36:06 -0800	[thread overview]
Message-ID: <CAHb6LvpCD0cQB1oGwV5S3rY1g=c9ezRvucy2Ks-U67jtCt8ncA@mail.gmail.com> (raw)
In-Reply-To: <87cz9dvkyf.fsf@toke.dk>


[-- Attachment #1.1: Type: text/plain, Size: 1543 bytes --]

Thanks Toke.

Bob

On Wed, Nov 23, 2022 at 5:50 AM Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> Bob McMahon <bob.mcmahon@broadcom.com> writes:
>
> > Does the TSQ code honor no-aggregation per voice access class or
> > TCP_NODELAY where the app making the socket write calls knows that the
> WiFi
> > aggregation isn't likely helpful? Sorry, my Linux stack expertise is
> quite
> > limited.
>
> TSQ only influences the buffering in the TCP layer. The WiFi stack will
> still limit aggregation using its own logic (I think it turns it off
> entirely for voice?). TCP_NODELAY is also orthogonal to TSQ; TSQ only
> kicks in when there's a bunch of data buffered, in which case
> TCP_NODELAY has no effect...
>
> -Toke
>

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #1.2: Type: text/html, Size: 2091 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]

  reply	other threads:[~2022-11-23 20:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22  6:04 [Bloat] " Dave Taht
2022-11-22 19:42 ` [Bloat] [bbr-dev] " Bob McMahon
2022-11-22 20:03   ` [Bloat] [Make-wifi-fast] " David Lang
2022-11-22 20:13     ` Bob McMahon
2022-11-22 20:16       ` David Lang
2022-11-22 20:28         ` Bob McMahon
2022-11-22 20:48           ` Bob McMahon
2022-11-22 20:10   ` [Bloat] " Neal Cardwell
2022-11-22 20:53     ` Toke Høiland-Jørgensen
2022-11-22 21:00       ` Bob McMahon
2022-11-23 13:50         ` Toke Høiland-Jørgensen
2022-11-23 20:36           ` Bob McMahon [this message]
     [not found]     ` <003d01d8ffc5$2ace1a20$806a4e60$@umt.edu.pk>
2022-11-24 16:23       ` 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/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='CAHb6LvpCD0cQB1oGwV5S3rY1g=c9ezRvucy2Ks-U67jtCt8ncA@mail.gmail.com' \
    --to=bob.mcmahon@broadcom.com \
    --cc=bbr-dev@googlegroups.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=ncardwell@google.com \
    --cc=toke@toke.dk \
    /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