Re: [PATCH 4/6] util: introduce co-shared-amount

2019-10-07 Thread Vladimir Sementsov-Ogievskiy
07.10.2019 18:22, Max Reitz wrote: > On 03.10.19 19:15, Vladimir Sementsov-Ogievskiy wrote: >> Introduce an API for some shared splitable resource, like memory. > > *splittable, I suppose > >> It's going to be used by backup. Backup uses both read/write io and >> copy_range. copy_range may consum

Re: [PATCH 4/6] util: introduce co-shared-amount

2019-10-07 Thread Max Reitz
On 03.10.19 19:15, Vladimir Sementsov-Ogievskiy wrote: > Introduce an API for some shared splitable resource, like memory. *splittable, I suppose > It's going to be used by backup. Backup uses both read/write io and > copy_range. copy_range may consume memory implictly, so new API is *the new AP

[PATCH 4/6] util: introduce co-shared-amount

2019-10-03 Thread Vladimir Sementsov-Ogievskiy
Introduce an API for some shared splitable 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 new API is abstract: it don't allocate any real memory but only handling out tickets. The idea is that we ha