Searched hist:"279 afbad4e54acbd61bf88a54a73af3bbfdeb5dd" (Results 1 – 7 of 7) sorted by relevance
/openbmc/linux/drivers/md/bcache/ |
H A D | writeback.h | 279afbad4e54acbd61bf88a54a73af3bbfdeb5dd Wed Jun 05 08:21:07 CDT 2013 Kent Overstreet <koverstreet@google.com> bcache: Track dirty data by stripe
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>
|
H A D | sysfs.c | diff 279afbad4e54acbd61bf88a54a73af3bbfdeb5dd Wed Jun 05 08:21:07 CDT 2013 Kent Overstreet <koverstreet@google.com> bcache: Track dirty data by stripe
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>
|
H A D | writeback.c | diff 279afbad4e54acbd61bf88a54a73af3bbfdeb5dd Wed Jun 05 08:21:07 CDT 2013 Kent Overstreet <koverstreet@google.com> bcache: Track dirty data by stripe
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>
|
H A D | bcache.h | diff 279afbad4e54acbd61bf88a54a73af3bbfdeb5dd Wed Jun 05 08:21:07 CDT 2013 Kent Overstreet <koverstreet@google.com> bcache: Track dirty data by stripe
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>
|
H A D | btree.c | diff 279afbad4e54acbd61bf88a54a73af3bbfdeb5dd Wed Jun 05 08:21:07 CDT 2013 Kent Overstreet <koverstreet@google.com> bcache: Track dirty data by stripe
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>
|
H A D | request.c | diff 279afbad4e54acbd61bf88a54a73af3bbfdeb5dd Wed Jun 05 08:21:07 CDT 2013 Kent Overstreet <koverstreet@google.com> bcache: Track dirty data by stripe
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>
|
H A D | super.c | diff 279afbad4e54acbd61bf88a54a73af3bbfdeb5dd Wed Jun 05 08:21:07 CDT 2013 Kent Overstreet <koverstreet@google.com> bcache: Track dirty data by stripe
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>
|