summaryrefslogtreecommitdiff
path: root/drivers/md/md.h
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2010-06-01 09:37:34 (GMT)
committerNeilBrown <neilb@suse.de>2010-07-26 03:21:34 (GMT)
commite384e58549a2e9a83071ad80280c1a9053cfd84c (patch)
tree805619143612ddc8cc71a45dd4522393c23a576f /drivers/md/md.h
parentef4256733506f2459a0c436b62267d22a3f0cec6 (diff)
downloadlinux-e384e58549a2e9a83071ad80280c1a9053cfd84c.tar.xz
md/bitmap: prepare for storing write-intent-bitmap via dm-dirty-log.
This allows md/raid5 to fully work as a dm target. Normally md uses a 'filemap' which contains a list of pages of bits each of which may be written separately. dm-log uses and all-or-nothing approach to writing the log, so when using a dm-log, ->filemap is NULL and the flags normally stored in filemap_attr are stored in ->logattrs instead. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/md.h')
-rw-r--r--drivers/md/md.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/drivers/md/md.h b/drivers/md/md.h
index 0a85078..cccbadb 100644
--- a/drivers/md/md.h
+++ b/drivers/md/md.h
@@ -317,6 +317,11 @@ struct mddev_s
* hot-adding a bitmap. It should
* eventually be settable by sysfs.
*/
+ /* When md is serving under dm, it might use a
+ * dirty_log to store the bits.
+ */
+ struct dm_dirty_log *log;
+
struct mutex mutex;
unsigned long chunksize;
unsigned long daemon_sleep; /* how many jiffies between updates? */