From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: virtio-fs-list <virtio-fs@redhat.com>
Subject: Re: [Virtio-fs] [PATCH V2] virtiofsd: Reset O_DIRECT flag during file open
Date: Thu, 22 Aug 2019 19:54:40 +0100 [thread overview]
Message-ID: <20190822185440.GN3277@work-vm> (raw)
In-Reply-To: <20190820183746.GF4233@redhat.com>
* Vivek Goyal (vgoyal@redhat.com) wrote:
> If an application wants to do direct IO and opens a file with O_DIRECT
> in guest, that does not necessarily mean that we need to bypass page
> cache on host as well. So reset this flag on host.
>
> If somebody needs to bypass page cache on host as well (and it is safe to
> do so), we can add a knob in daemon later to control this behavior.
>
> I check virtio-9p and they do reset O_DIRECT flag.
>
> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Merged; thanks
> ---
> contrib/virtiofsd/passthrough_ll.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> Index: qemu/contrib/virtiofsd/passthrough_ll.c
> ===================================================================
> --- qemu.orig/contrib/virtiofsd/passthrough_ll.c 2019-08-20 09:33:07.900975145 -0400
> +++ qemu/contrib/virtiofsd/passthrough_ll.c 2019-08-20 14:31:39.725781357 -0400
> @@ -1752,6 +1752,13 @@ static void lo_create(fuse_req_t req, fu
> if (err)
> goto out;
>
> + /*
> + * O_DIRECT in guest should not necessarily mean bypassing page
> + * cache on host as well. If somebody needs that behavior, it
> + * probably should be a configuration knob in daemon.
> + */
> + fi->flags &= ~O_DIRECT;
> +
> fd = openat(parent_inode->fd, name,
> (fi->flags | O_CREAT) & ~O_NOFOLLOW, mode);
> err = fd == -1 ? errno : 0;
> @@ -1967,6 +1974,13 @@ static void lo_open(fuse_req_t req, fuse
> if (lo->writeback && (fi->flags & O_APPEND))
> fi->flags &= ~O_APPEND;
>
> + /*
> + * O_DIRECT in guest should not necessarily mean bypassing page
> + * cache on host as well. If somebody needs that behavior, it
> + * probably should be a configuration knob in daemon.
> + */
> + fi->flags &= ~O_DIRECT;
> +
> sprintf(buf, "%i", lo_fd(req, ino));
> fd = openat(lo->proc_self_fd, buf, fi->flags & ~O_NOFOLLOW);
> if (fd == -1)
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2019-08-22 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 18:37 [Virtio-fs] [PATCH V2] virtiofsd: Reset O_DIRECT flag during file open Vivek Goyal
2019-08-22 13:15 ` Stefan Hajnoczi
2019-08-22 18:54 ` 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=20190822185440.GN3277@work-vm \
--to=dgilbert@redhat.com \
--cc=vgoyal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.