Home
last modified time | relevance | path

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

/Linux-v5.4/drivers/md/
Ddm-integrity.c65 __u64 provided_data_sectors; /* userspace uses this value */ member
184 sector_t provided_data_sectors; member
1644 if (unlikely(dio->range.logical_sector + bio_sectors(bio) > ic->provided_data_sectors)) { in dm_integrity_map()
1647 (unsigned long long)ic->provided_data_sectors); in dm_integrity_map()
2378 if (unlikely(range.logical_sector >= ic->provided_data_sectors)) { in integrity_recalc()
2387 range.n_sectors = min((sector_t)RECALC_SECTORS, ic->provided_data_sectors - range.logical_sector); in integrity_recalc()
2538 range.n_sectors = ic->provided_data_sectors; in bitmap_flush_work()
2548 limit = ic->provided_data_sectors; in bitmap_flush_work()
2853 if (!block_bitmap_op(ic, ic->journal, 0, ic->provided_data_sectors, in dm_integrity_resume()
2862 block_bitmap_op(ic, ic->recalc_bitmap, 0, ic->provided_data_sectors, BITMAP_OP_SET); in dm_integrity_resume()
[all …]
/Linux-v5.4/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"