Re: [Bloat] using tcp_notsent_lowat in various apps?

[Eric Dumazet <eric.dumazet@gmail.com>]

On Sun, 2015-06-21 at 17:04 +0200, Juliusz Chroboczek wrote:

> 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.

Unless you have thousands of tcp flows maybe, where (unswapable) kernel
memory becomes a precious resource.

Of course, if you have a few tcp sockets, just queuing 10 Mbytes per
socket will be your best shot, in terms of cpu overhead (one schedule
every 5 MBytes or so)