Re: [virtio-dev] [PATCH v7 2/2] virtio-fs: add DAX window

On Mon, Aug 26, 2019 at 03:28:52PM +0200, Cornelia Huck wrote: > On Fri, 23 Aug 2019 16:39:40 +0100 > Stefan Hajnoczi wrote: > > > Describe how shared memory region ID 0 is the DAX window and how > > FUSE_SETUPMAPPING maps file ranges into the window. > > > > Signed-off-by: Stefan Hajnoczi > >

Re: [virtio-dev] [PATCH v8 2/2] virtio-fs: add DAX window

On Thu, 29 Aug 2019 14:52:06 +0100 Stefan Hajnoczi wrote: > Describe how shared memory region ID 0 is the DAX window and how > FUSE_SETUPMAPPING maps file ranges into the window. > > Signed-off-by: Stefan Hajnoczi > --- > The FUSE_SETUPMAPPING message is part of the virtio-fs Linux patches: >

[virtio-dev] [PATCH v8 1/2] content: add virtio file system device

The virtio file system device transports Linux FUSE requests between a FUSE daemon running on the host and the FUSE driver inside the guest. The actual FUSE request definitions are not duplicated in the virtio specification, similar to how virtio-scsi does not document SCSI command details. FUSE

[virtio-dev] [PATCH v8 2/2] virtio-fs: add DAX window

Describe how shared memory region ID 0 is the DAX window and how FUSE_SETUPMAPPING maps file ranges into the window. Signed-off-by: Stefan Hajnoczi --- The FUSE_SETUPMAPPING message is part of the virtio-fs Linux patches:

[virtio-dev] [PATCH v8 0/2] virtio-fs: add virtio file system device

v8: * Make language about using both FUSE_READ/FUSE_WRITE and the DAX Window clearer [Cornelia] v7: * Rename num_queues to num_request_queues [Cornelia] * Clarify that endianness is chosen by the guest driver in the FUSE_INIT message [Cornelia] * Clarify that the DAX Window is optional