[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bcc94e61-d4ce-4a33-a7cd-0cb61a516bf9@linux.alibaba.com>
Date: Wed, 18 Dec 2024 11:35:19 +0800
From: Ferry Meng <mengferry@...ux.alibaba.com>
To: Jens Axboe <axboe@...nel.dk>, Stefan Hajnoczi <stefanha@...il.com>
Cc: Jingbo Xu <jefflexu@...ux.alibaba.com>,
Christoph Hellwig <hch@...radead.org>, "Michael S . Tsirkin"
<mst@...hat.com>, Jason Wang <jasowang@...hat.com>,
linux-block@...r.kernel.org, virtualization@...ts.linux.dev,
linux-kernel@...r.kernel.org, io-uring@...r.kernel.org,
Joseph Qi <joseph.qi@...ux.alibaba.com>
Subject: Re: [PATCH 0/3][RFC] virtio-blk: add io_uring passthrough support for
virtio-blk
On 12/18/24 5:07 AM, Jens Axboe wrote:
> On 12/17/24 2:00 PM, Stefan Hajnoczi wrote:
>> On Tue, 17 Dec 2024 at 12:54, Jens Axboe <axboe@...nel.dk> wrote:
>>> On 12/16/24 11:08 PM, Jingbo Xu wrote:
>>>>> That's why I asked Jens to weigh in on whether there is a generic
>>>>> block layer solution here. If uring_cmd is faster then maybe a generic
>>>>> uring_cmd I/O interface can be defined without tying applications to
>>>>> device-specific commands. Or maybe the traditional io_uring code path
>>>>> can be optimized so that bypass is no longer attractive.
>>> It's not that the traditional io_uring code path is slower, it's in fact
>>> basically the same thing. It's that all the other jazz that happens
>>> below io_uring slows things down, which is why passthrough ends up being
>>> faster.
>> Are you happy with virtio_blk passthrough or do you want a different approach?
> I think it looks fine.
>
OK, thx. I will submit the official patch for review soon after
resolving the test bot warning.
Powered by blists - more mailing lists