From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <david@lang.hm>
Received: from bifrost.lang.hm (lang.hm [66.167.227.134])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id 566593B4D2
 for <bloat@lists.bufferbloat.net>; Thu, 14 Apr 2016 20:40:33 -0400 (EDT)
Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100])
 by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id u3F0ePId021990
 for <bloat@lists.bufferbloat.net>; Thu, 14 Apr 2016 17:40:30 -0700
Date: Thu, 14 Apr 2016 17:40:25 -0700 (PDT)
From: David Lang <david@lang.hm>
X-X-Sender: dlang@asgard.lang.hm
To: bloat@lists.bufferbloat.net
Message-ID: <alpine.DEB.2.02.1604141738510.9471@nftneq.ynat.uz>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Subject: [Bloat] bloat in linux disk I/O stack
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
 <mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
 <mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2016 00:40:33 -0000

This lwn.net article about writeback problems correctly draws parallels with 
networking and bufferbloat

https://lwn.net/SubscriberLink/682582/96676d064f4bce65/

Toward less-annoying background writeback

David Lang