diff options
author | Wu Fengguang <fengguang.wu@intel.com> | 2010-08-29 19:28:09 (GMT) |
---|---|---|
committer | Wu Fengguang <fengguang.wu@intel.com> | 2011-07-10 05:09:03 (GMT) |
commit | 1a12d8bd7b2998be01ee55edb64e7473728abb9c (patch) | |
tree | d3466ea7eaa308e3d40a43e372bd4baaf461d7bb /drivers/mmc | |
parent | e1cbe236013c82bcf9a156e98d7b47efb89d2674 (diff) | |
download | linux-fsl-qoriq-1a12d8bd7b2998be01ee55edb64e7473728abb9c.tar.xz |
writeback: scale IO chunk size up to half device bandwidth
Originally, MAX_WRITEBACK_PAGES was hard-coded to 1024 because of a
concern of not holding I_SYNC for too long. (At least, that was the
comment previously.) This doesn't make sense now because the only
time we wait for I_SYNC is if we are calling sync or fsync, and in
that case we need to write out all of the data anyway. Previously
there may have been other code paths that waited on I_SYNC, but not
any more. -- Theodore Ts'o
So remove the MAX_WRITEBACK_PAGES constraint. The writeback pages
will adapt to as large as the storage device can write within 500ms.
XFS is observed to do IO completions in a batch, and the batch size is
equal to the write chunk size. To avoid dirty pages to suddenly drop
out of balance_dirty_pages()'s dirty control scope and create large
fluctuations, the chunk size is also limited to half the control scope.
The balance_dirty_pages() control scrope is
[(background_thresh + dirty_thresh) / 2, dirty_thresh]
which is by default [15%, 20%] of global dirty pages, whose range size
is dirty_thresh / DIRTY_FULL_SCOPE.
The adpative write chunk size will be rounded to the nearest 4MB
boundary.
http://bugzilla.kernel.org/show_bug.cgi?id=13930
CC: Theodore Ts'o <tytso@mit.edu>
CC: Dave Chinner <david@fromorbit.com>
CC: Chris Mason <chris.mason@oracle.com>
CC: Peter Zijlstra <a.p.zijlstra@chello.nl>
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
Diffstat (limited to 'drivers/mmc')
0 files changed, 0 insertions, 0 deletions