[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACGkMEtdMzr1chpneCTnpjHFKaN5YSZbsVjSLtHSt+ULpUHG4g@mail.gmail.com>
Date: Thu, 23 Jan 2025 09:49:56 +0800
From: Jason Wang <jasowang@...hat.com>
To: Stefan Hajnoczi <stefanha@...hat.com>
Cc: Eugenio Pérez <eperezma@...hat.com>, mst@...hat.com,
virtualization@...ts.linux.dev, linux-kernel@...r.kernel.org,
Hanna Reitz <hreitz@...hat.com>, Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
German Maglione <gmaglione@...hat.com>
Subject: Re: [PATCH] vduse: add virtio_fs to allowed dev id
On Wed, Jan 22, 2025 at 11:49 PM Stefan Hajnoczi <stefanha@...hat.com> wrote:
>
> On Tue, Jan 21, 2025 at 11:33:46AM +0100, Eugenio Pérez wrote:
> > A VDUSE device that implements virtiofs device works fine just by
> > adding the device id to the whitelist.
>
> The virtiofs DAX Window feature might require extra work. It is not
> widely enabled though, so must virtiofs devices will work fine with just
> virtqueue and configuration space support.
+1.
The DAX Window may help to reduce the bounce buffer copying and fit
for the case where an AI application just accesses one single large
file.
We need to consider implementing this via VDUSE.
Thanks
>
> Reviewed-by: Stefan Hajnoczi <stefanha@...hat.com>
Powered by blists - more mailing lists