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: Mon, 22 Jun 2015 14:05:23 +0200 [thread overview]
Message-ID: <87h9q02bjw.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <1434956529.4110.1.camel@edumazet-glaptop2.roam.corp.google.com>
>> amount of buffering depends on the kernel latency, and hence should be
>> better done by the kernel itself.
> Unless you have thousands of tcp flows maybe, where (unswapable) kernel
> memory becomes a precious resource.
Thanks, that makes sense.
-- Juliusz
prev parent reply other threads:[~2015-06-22 12:05 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
2015-06-21 16:09 ` Jonathan Morton
2015-06-22 7:02 ` Eric Dumazet
2015-06-22 12:05 ` Juliusz Chroboczek [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=87h9q02bjw.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