Dear Kevin, Kevin Wolf <kw...@redhat.com> writes:
> Am 08.04.2016 um 14:01 hat Sascha Silbe geschrieben: [...] >> The best approach probably would be to fix up the rate limit code to >> delay for multiple time slices if necessary. We should get rid of the >> artificial BDRV_SECTOR_SIZE granularity at the same time, always using >> bytes as the quantum unit. > > In the 2.7 time frame we might actually be able to reuse the normal I/O > throttling code for block jobs as the jobs will be using their own > BlockBackend and can therefore set their own throttling limits. Sounds good. Then I suggest we just drop this patch for now. I've added a reminder to check the situation again at the end of June (i.e. before soft feature freeze of 2.7). Will give documenting the minimum rate a try, but that shouldn't hold up the fixes. Sascha -- Softwareentwicklung Sascha Silbe, Niederhofenstraße 5/1, 71229 Leonberg https://se-silbe.de/ USt-IdNr. DE281696641
