Re: [PATCH 14/45] writeback: quit on wrap for .range_cyclic (afs)

[Nick Piggin]

On Wed, Oct 07, 2009 at 06:47:11PM +0800, Wu Fengguang wrote:
> On Wed, Oct 07, 2009 at 06:21:30PM +0800, Nick Piggin wrote:
> > On Wed, Oct 07, 2009 at 11:17:06AM +0100, David Howells wrote:
> > > Wu Fengguang <fengguang.wu@xxxxxxxxx> wrote:
> > > 
> > > > Convert wbc.range_cyclic to new behavior: when past EOF, abort writeback
> > > > of the inode, which instructs writeback_single_inode() to delay it for
> > > > a while if necessary.
> > > > 
> > > > It removes one inefficient .range_cyclic IO pattern when writeback_index
> > > > wraps:
> > > > 	submit [10000-10100], (wrap), submit [0-100]
> > > > In which the submitted pages may be consisted of two distant ranges.
> > > > 
> > > > It also prevents submitting pointless IO for busy overwriters.
> > > > 
> > > > CC: David Howells <dhowells@xxxxxxxxxx>
> > > > Signed-off-by: Wu Fengguang <fengguang.wu@xxxxxxxxx>
> > > 
> > > Acked-by: David Howells <dhowells@xxxxxxxxxx>
> > 
> > I don't see why. Then the inode is given less write bandwidth than
> > those which don't wrap (or wrap on "nice" boundaries).
> 
> The "return on wrapped" behavior itself only offers a natural seek
> boundary to the upper layer.  It's mainly the "whether to delay"
> policy that will affect (overall) bandwidth.
> 
> If we choose to not sleep, and to go on with other inodes and then
> back to this inode, no bandwidth will be lost.
> 
> If we have done work with other inodes (if any), and choose to sleep
> for a while before restarting this inode, then we could lose bandwidth.
> The plus side is, we possibly avoid submitting extra IO if this inode
> is being busy overwritten. So it's a tradeoff.
> 
> The behavior after this patchset is, to keep busy as long as we can
> write any pages (in patch 38/45). So we still opt for bandwidth :)

No I mean bandwidth fairness between inodes.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/