Re: [PATCH v4 05/11] block: use int64_t instead of uint64_t in copy_range driver handlers

2021-05-11 Thread Eric Blake
On 3/24/21 3:51 PM, Vladimir Sementsov-Ogievskiy wrote: > We are generally moving to int64_t for both offset and bytes parameters > on all io paths. > > Main motivation is realization of 64-bit write_zeroes operation for > fast zeroing large disk chunks, up to the whole disk. > > We chose signed

[PATCH v4 05/11] block: use int64_t instead of uint64_t in copy_range driver handlers

2021-03-24 Thread Vladimir Sementsov-Ogievskiy
We are generally moving to int64_t for both offset and bytes parameters on all io paths. Main motivation is realization of 64-bit write_zeroes operation for fast zeroing large disk chunks, up to the whole disk. We chose signed type, to be consistent with off_t (which is signed) and with