From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: piaojun <piaojun@huawei.com>
Cc: virtio-fs@redhat.com
Subject: Re: [Virtio-fs] [PATCH v2 2/2][RFC] use fuse_buf_writev to replace fuse_buf_write for better performance
Date: Thu, 8 Aug 2019 09:23:36 +0100 [thread overview]
Message-ID: <20190808082336.GA2852@work-vm> (raw)
In-Reply-To: <5D4B7A28.4090504@huawei.com>
* piaojun (piaojun@huawei.com) wrote:
> Hi Dave,
>
> On 2019/8/7 23:37, Dr. David Alan Gilbert wrote:
> > * piaojun (piaojun@huawei.com) wrote:
> >> fuse_buf_writev() only handles the normal write in which src is buffer
> >> and dest is fd. Specially if src buffer represents guest physical
> >> address that can't be mapped by the daemon process, IO must be bounced
> >> back to the VMM to do it by fuse_buf_copy().
> >>
> >> Signed-off-by: Jun Piao <piaojun@huawei.com>
> >> Suggested-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> >> ---
> >> contrib/virtiofsd/passthrough_ll.c | 5 ++++-
> >> 1 file changed, 4 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/contrib/virtiofsd/passthrough_ll.c b/contrib/virtiofsd/passthrough_ll.c
> >> index cc9c175..c1bbc53 100644
> >> --- a/contrib/virtiofsd/passthrough_ll.c
> >> +++ b/contrib/virtiofsd/passthrough_ll.c
> >> @@ -2023,7 +2023,10 @@ static void lo_write_buf(fuse_req_t req, fuse_ino_t ino,
> >> fuse_debug("lo_write_buf(ino=%" PRIu64 ", size=%zd, off=%lu)\n",
> >> ino, out_buf.buf[0].size, (unsigned long) off);
> >>
> >> - res = fuse_buf_copy(req, &out_buf, in_buf, 0);
> >> + if (!(in_buf->buf[0].flags & FUSE_BUF_PHYS_ADDR))
> >
> > I don't think you can assume that the flags in in_buf[0] represent the
> > state of the entire vector; I'm pretty sure we had a case of an
> > application that did a writev() in the guest where the first element was
> > on the stack and the other was in an mmap, and it was only the 2nd one
> > that had the flag.
>
> Yes, this assumption is idealized, and perhaps I need check all the
> flags of entire vector before doing writev, right?
Yes, you need to make sure that the vector fits the nice easy
sequential case for pwritev.
Dave
> Thanks,
> Jun
>
> >
> > But also you're not checking any of the other flags either.
> >
> > Dave
> >
> >> + res = fuse_buf_writev(req, &out_buf, in_buf, out_buf.buf[0].flags);
> >> + else
> >> + res = fuse_buf_copy(req, &out_buf, in_buf, 0);
> >> if(res < 0) {
> >> fuse_reply_err(req, -res);
> >> } else {
> >> --
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> > .
> >
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2019-08-08 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 7:10 [Virtio-fs] [PATCH v2 2/2][RFC] use fuse_buf_writev to replace fuse_buf_write for better performance piaojun
2019-08-07 9:21 ` Stefan Hajnoczi
2019-08-07 9:58 ` piaojun
2019-08-07 15:37 ` Dr. David Alan Gilbert
2019-08-08 1:26 ` piaojun
2019-08-08 8:23 ` 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=20190808082336.GA2852@work-vm \
--to=dgilbert@redhat.com \
--cc=piaojun@huawei.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.