[Bloat] sweeping up the bloat

[Dave Taht <dave.taht@gmail.com>]

In a larger context, I was also trying to find ways to describe and
offload a set of simple tasks (like adding BQL and this), and to find
ways to enthuse folk about tackling them, at scale. We shouldn't have
to sweat the small stuff so much.

So this is my preliminary list:

http://www.bufferbloat.net/projects/bloat/wiki/Janitorial_Tasks

Any additions or suggestions for text welcomed. What other easy stuff
can be hit across the board using the bufferbloat-fighting facilities
that have landed in Linux?

As one example: I don't have a firm guideline for how, why or when or
when to enable pacing - so far as I know the patch(es) for xvnc is
still out of tree?


On Tue, Jun 16, 2015 at 9:33 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 16 Jun, 2015, at 19:18, Steinar H. Gunderson <sgunderson@bigfoot.com> wrote:
>>
>> On Tue, Jun 16, 2015 at 09:11:08AM -0700, Dave Taht wrote:
>>> I just tossed off a quick patch for rsync, not that I have a clue as
>>> to whether it would make any difference there.
>>
>> For bulk applications (like rsync), how would this make sense at all?
>> I thought the entire point of this option was if you knew what data to send
>> now, but that you might want to change your mind later if it takes some time
>> to send it. The latter doesn't apply to rsync.
>
> Actually, it does.  Rsync is designed to be used to update an existing set of files, so the protocol interleaves control and data information asynchronously.
>
> More generally, I think it’s worth setting LOWAT on *any* application that uses select() or poll() with a readable and writable socket population simultaneously.
>
> - Jonathan Morton
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat



-- 
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast