linux-stable.git/drivers/md/bcache/writeback.h, branch linux-3.13.y Linux kernel stable tree bcache: Fix sysfs splat on shutdown with flash only devs 2013-11-11T05:56:41+00:00 Kent Overstreet kmo@daterainc.com 2013-08-22T00:49:09+00:00 c4d951ddb66fe1d087447b0ba65c4fa4446f1083 Whoops. Signed-off-by: Kent Overstreet <kmo@daterainc.com> 
Whoops.

Signed-off-by: Kent Overstreet <kmo@daterainc.com>
bcache: Better full stripe scanning 2013-11-11T05:56:41+00:00 Kent Overstreet kmo@daterainc.com 2013-10-31T22:43:22+00:00 48a915a87f0bd98c3d68d029acf223a2e5116f07 The old scanning-by-stripe code burned too much CPU, this should be better. Signed-off-by: Kent Overstreet <kmo@daterainc.com> 
The old scanning-by-stripe code burned too much CPU, this should be
better.

Signed-off-by: Kent Overstreet <kmo@daterainc.com>
bcache: Convert writeback to a kthread 2013-11-11T05:56:05+00:00 Kent Overstreet kmo@daterainc.com 2013-07-25T00:50:06+00:00 5e6926daac267dd99552ae613f041a9e88bbf258 This simplifies the writeback flow control quite a bit - previously, it was conceptually two coroutines, refill_dirty() and read_dirty(). This makes the code quite a bit more straightforward. Signed-off-by: Kent Overstreet <kmo@daterainc.com> 
This simplifies the writeback flow control quite a bit - previously, it
was conceptually two coroutines, refill_dirty() and read_dirty(). This
makes the code quite a bit more straightforward.

Signed-off-by: Kent Overstreet <kmo@daterainc.com>
bcache: Stripe size isn't necessarily a power of two 2013-11-11T05:55:55+00:00 Kent Overstreet kmo@daterainc.com 2013-08-17T09:13:15+00:00 2d679fc75678551485df62274edaed452becd16d Originally I got this right... except that the divides didn't use do_div(), which broke 32 bit kernels. When I went to fix that, I forgot that the raid stripe size usually isn't a power of two... doh Signed-off-by: Kent Overstreet <kmo@daterainc.com> 
Originally I got this right... except that the divides didn't use
do_div(), which broke 32 bit kernels. When I went to fix that, I forgot
that the raid stripe size usually isn't a power of two... doh

Signed-off-by: Kent Overstreet <kmo@daterainc.com>
bcache: Write out full stripes 2013-06-27T04:58:04+00:00 Kent Overstreet koverstreet@google.com 2013-06-05T13:24:39+00:00 72c270612bd33192fa836ad0f2939af1ca218292 Now that we're tracking dirty data per stripe, we can add two optimizations for raid5/6: * If a stripe is already dirty, force writes to that stripe to writeback mode - to help build up full stripes of dirty data * When flushing dirty data, preferentially write out full stripes first if there are any. Signed-off-by: Kent Overstreet <koverstreet@google.com> 
Now that we're tracking dirty data per stripe, we can add two
optimizations for raid5/6:

 * If a stripe is already dirty, force writes to that stripe to
   writeback mode - to help build up full stripes of dirty data

 * When flushing dirty data, preferentially write out full stripes first
   if there are any.

Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Track dirty data by stripe 2013-06-27T04:57:23+00:00 Kent Overstreet koverstreet@google.com 2013-06-05T13:21:07+00:00 279afbad4e54acbd61bf88a54a73af3bbfdeb5dd To make background writeback aware of raid5/6 stripes, we first need to track the amount of dirty data within each stripe - we do this by breaking up the existing sectors_dirty into per stripe atomic_ts Signed-off-by: Kent Overstreet <koverstreet@google.com> 
To make background writeback aware of raid5/6 stripes, we first need to
track the amount of dirty data within each stripe - we do this by
breaking up the existing sectors_dirty into per stripe atomic_ts

Signed-off-by: Kent Overstreet <koverstreet@google.com>