May not accept 0 as the offset?

[akiradeveloper]

This is what came up with when reading the code.

In this example of initialization dmsetup create wbdev --table "0 $sz writeboost $BACKING $CACHE 2 writeback_threshold 70", the number 0 after the word table is called offset. It should be able to accept number other than 0.

But the current Writeboost may only accept 0. I think all users now set the number to 0. Waiting for user report.

[akiradeveloper]

The test in writeboost-test-suite uses 0 as the offset. s"0 ${backingDev.bdev.size} writeboost ${backingDev.bdev.path} ${cacheDev.bdev.path}" + optionalArgs but to change this number will cause wide range of changes in other codebase. I don't think it's worthy.

[akiradeveloper]

The motivation to use offset other than 0 is creating a large virtual device that is concatenating multiple virtual devices or mappings. When implementing linear target, it sounds essential but for caching target it doesn't for me. As a fact, dm-cache target seems to be ignoring this because it doesn't use dm_target_offset function in it.