Home
last modified time | relevance | path

Searched refs:provided_data_sectors (Results 1 – 2 of 2) sorted by relevance

/linux-6.1.9/drivers/md/
Ddm-integrity.c73 __le64 provided_data_sectors; /* userspace uses this value */ member
198 sector_t provided_data_sectors; member
1894 if (unlikely(dio->range.logical_sector + bio_sectors(bio) > ic->provided_data_sectors)) { in dm_integrity_map()
1897 ic->provided_data_sectors); in dm_integrity_map()
2479 if (unlikely(sec >= ic->provided_data_sectors)) { in do_journal_write()
2493 if (unlikely(sec2 >= ic->provided_data_sectors)) in do_journal_write()
2659 if (unlikely(range.logical_sector >= ic->provided_data_sectors)) { in integrity_recalc()
2661 block_bitmap_op(ic, ic->recalc_bitmap, 0, ic->provided_data_sectors, BITMAP_OP_CLEAR); in integrity_recalc()
2669 range.n_sectors = min((sector_t)RECALC_SECTORS, ic->provided_data_sectors - range.logical_sector); in integrity_recalc()
2830 range.n_sectors = ic->provided_data_sectors; in bitmap_flush_work()
[all …]
/linux-6.1.9/Documentation/admin-guide/device-mapper/
Ddm-integrity.rst47 4. read the "provided_data_sectors" value from the superblock
49 "provided_data_sectors"
51 with the size "provided_data_sectors"