aboutsummaryrefslogtreecommitdiffstats
path: root/block/blk-lib.c
diff options
context:
space:
mode:
authorMikulas Patocka <mpatocka@redhat.com>2019-04-29 14:57:24 +0200
committerMike Snitzer <snitzer@redhat.com>2019-05-08 13:41:58 -0400
commit468dfca38b1a6fbdccd195d875599cb7c8875cd9 (patch)
tree607472ff36499f4d1203fd12b74654c7ae7aba76 /block/blk-lib.c
parentdm integrity: introduce a function add_new_range_and_wait() (diff)
downloadlinux-dev-468dfca38b1a6fbdccd195d875599cb7c8875cd9.tar.xz
linux-dev-468dfca38b1a6fbdccd195d875599cb7c8875cd9.zip
dm integrity: add a bitmap mode
Introduce an alternate mode of operation where dm-integrity uses a bitmap instead of a journal. If a bit in the bitmap is 1, the corresponding region's data and integrity tags are not synchronized - if the machine crashes, the unsynchronized regions will be recalculated. The bitmap mode is faster than the journal mode, because we don't have to write the data twice, but it is also less reliable, because if data corruption happens when the machine crashes, it may not be detected. Benchmark results for an SSD connected to a SATA300 port, when doing large linear writes with dd: buffered I/O: raw device throughput - 245MB/s dm-integrity with journaling - 120MB/s dm-integrity with bitmap - 238MB/s direct I/O with 1MB block size: raw device throughput - 248MB/s dm-integrity with journaling - 123MB/s dm-integrity with bitmap - 223MB/s For more info see dm-integrity in Documentation/device-mapper/ Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'block/blk-lib.c')
0 files changed, 0 insertions, 0 deletions