On Thu 2016-09-15 10:43:54, Josef Bacik wrote:
> NBD can become contended on its single connection. We have to serialize all
> writes and we can only process one read response at a time. Fix this by
> allowing userspace to provide multiple connections to a single nbd device. This
> coupled with block-mq drastically increases performance in multi-process cases.
> Thanks,
>
> Signed-off-by: Josef Bacik <[email protected]>
Idea is that it can now use multiple CPUs concurrently...?
Do you have a diff for the nbd-server, too?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On 10/07/2016 02:36 PM, Pavel Machek wrote:
> On Thu 2016-09-15 10:43:54, Josef Bacik wrote:
>> NBD can become contended on its single connection. We have to serialize all
>> writes and we can only process one read response at a time. Fix this by
>> allowing userspace to provide multiple connections to a single nbd device. This
>> coupled with block-mq drastically increases performance in multi-process cases.
>> Thanks,
>>
>> Signed-off-by: Josef Bacik <[email protected]>
>
> Idea is that it can now use multiple CPUs concurrently...?
>
> Do you have a diff for the nbd-server, too?
> Pavel
>
nbd-server doesn't need anything special, it just works. I have a patch for
nbd-client so you can open multiple connections to setup the NBD device. You
can find my patches for the userspace stuff here
https://github.com/josefbacik/nbd
Thanks,
Josef