22.10.2019 13:23, Max Reitz wrote:
> On 16.10.19 19:09, Vladimir Sementsov-Ogievskiy wrote:
>> Introduce an API for some shared splittable resource, like memory.
>> It's going to be used by backup. Backup uses both read/write io and
>> copy_range. copy_range may consume memory implictly, so the new
On 16.10.19 19:09, Vladimir Sementsov-Ogievskiy wrote:
> Introduce an API for some shared splittable resource, like memory.
> It's going to be used by backup. Backup uses both read/write io and
> copy_range. copy_range may consume memory implictly, so the new API is
> abstract: it doesn't allocate
Introduce an API for some shared splittable resource, like memory.
It's going to be used by backup. Backup uses both read/write io and
copy_range. copy_range may consume memory implictly, so the new API is
abstract: it doesn't allocate any real memory by but only hands out
tickets.
The idea is tha
