From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-fs@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] virtiofsd: add FUSE_INIT map_alignment field
Date: Mon, 29 Jul 2019 10:25:02 +0100 [thread overview]
Message-ID: <20190729092502.GA2756@work-vm> (raw)
In-Reply-To: <20190726083322.13637-1-stefanha@redhat.com>
* Stefan Hajnoczi (stefanha@redhat.com) wrote:
> The client must know the server's alignment constraints for FUSE_SETUPMAPPING
> and FUSE_REMOVEMAPPING. This is necessary because mmap(2)/munmap(2) have
> alignment constraints and the guest may have a different page size from the
> host. The new FUSE_INIT map_alignment field communicates this information to
> the client.
OK, merged into my local world.
DAve
> Stefan Hajnoczi (3):
> virtiofsd: sync up fuse.h Linux 5.1 header
> virtiofsd: add map_alignment to fuse_kernel.h
> virtiofsd: implement FUSE_INIT map_alignment field
>
> contrib/virtiofsd/fuse_kernel.h | 56 +++++++++++++++++++++----------
> contrib/virtiofsd/fuse_lowlevel.c | 8 +++++
> 2 files changed, 47 insertions(+), 17 deletions(-)
>
> --
> 2.21.0
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2019-07-29 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 8:33 [Qemu-devel] [PATCH 0/3] virtiofsd: add FUSE_INIT map_alignment field Stefan Hajnoczi
2019-07-26 8:33 ` [Qemu-devel] [PATCH 1/3] virtiofsd: sync up fuse.h Linux 5.1 header Stefan Hajnoczi
2019-07-26 8:33 ` [Qemu-devel] [PATCH 2/3] virtiofsd: add map_alignment to fuse_kernel.h Stefan Hajnoczi
2019-07-26 8:33 ` [Qemu-devel] [PATCH 3/3] virtiofsd: implement FUSE_INIT map_alignment field Stefan Hajnoczi
2019-07-29 9:25 ` Dr. David Alan Gilbert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190729092502.GA2756@work-vm \
--to=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=virtio-fs@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).