General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] using tcp_notsent_lowat in various apps?
Date: Sun, 21 Jun 2015 17:04:50 +0200	[thread overview]
Message-ID: <87y4jd3xwt.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <1434697811.31511.9.camel@edumazet-glaptop2.roam.corp.google.com>

[Removed bloat-devel from the CC]

> [1] Already sent data [...]
> [2] Not sent data.

[...]

> While NOTSENT_LOWAT is able to restrict (2) only, avoiding filling write 
> queue when/if no drops are actually seen.

Thanks for the explanation, Eric.

Do you have any concrete examples where this has been found to yield 
better results than what the kernel can do on its own?  I'm probably 
missing something, but my intuition is that conversational protocols 
should be naturally self-pacing, while for streaming protocols the right 
amount of buffering depends on the kernel latency, and hence should be 
better done by the kernel itself.

-- Juliusz

  reply	other threads:[~2015-06-21 15:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 16:11 Dave Taht
2015-06-16 16:18 ` Steinar H. Gunderson
2015-06-16 16:31   ` Dave Taht
2015-06-16 16:33   ` Jonathan Morton
2015-06-16 17:22     ` Dave Taht
2015-06-16 18:12       ` Eric Dumazet
2015-06-19  2:47 ` Juliusz Chroboczek
2015-06-19  4:07   ` Jonathan Morton
2015-06-19  7:10     ` Eric Dumazet
2015-06-21 15:04       ` Juliusz Chroboczek [this message]
2015-06-21 16:09         ` Jonathan Morton
2015-06-22  7:02         ` Eric Dumazet
2015-06-22 12:05           ` Juliusz Chroboczek

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=87y4jd3xwt.wl-jch@pps.univ-paris-diderot.fr \
    --to=jch@pps.univ-paris-diderot.fr \
    --cc=bloat@lists.bufferbloat.net \
    --cc=eric.dumazet@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