[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJSP0QWfSzD8Z+22SEjUMkG07nrBa+6WU_APYkrvwzNbScRRCw@mail.gmail.com>
Date: Tue, 17 Dec 2024 16:00:37 -0500
From: Stefan Hajnoczi <stefanha@...il.com>
To: Jens Axboe <axboe@...nel.dk>
Cc: Jingbo Xu <jefflexu@...ux.alibaba.com>, Christoph Hellwig <hch@...radead.org>,
Ferry Meng <mengferry@...ux.alibaba.com>, "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 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?
Stefan
Powered by blists - more mailing lists