All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: virtio-fs@redhat.com, Peng Tao <tao.peng@linux.alibaba.com>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [Virtio-fs] [PATCH] virtiofsd: make FUSE_REMOVEMAPPING support multiple entries
Date: Wed, 22 May 2019 12:38:33 +0100	[thread overview]
Message-ID: <20190522113832.GD2666@work-vm> (raw)
In-Reply-To: <CAOssrKchxy0EU=6Gb2uDj3MeCYrLMkmsBE8p6hMAQ=TG9-JmpQ@mail.gmail.com>

* Miklos Szeredi (mszeredi@redhat.com) wrote:
> On Wed, May 22, 2019 at 1:27 PM Dr. David Alan Gilbert
> <dgilbert@redhat.com> wrote:
> >
> > * Peng Tao (tao.peng@linux.alibaba.com) wrote:
> > > The fuse wire protocol is changed so that we can unmap multiple
> > > mappings in a single call.
> > >
> > > Signed-off-by: Peng Tao <tao.peng@linux.alibaba.com>
> >
> > Hi,
> >   Thanks for the patch and apologies for not responding sooner
> >
> > > ---
> > >  contrib/virtiofsd/fuse_kernel.h    |  9 +++++++--
> > >  contrib/virtiofsd/fuse_lowlevel.c  | 21 ++++++++++++++------
> > >  contrib/virtiofsd/fuse_lowlevel.h  |  5 +++--
> > >  contrib/virtiofsd/passthrough_ll.c | 31 ++++++++++++++++++++----------
> > >  4 files changed, 46 insertions(+), 20 deletions(-)
> > >
> > > diff --git a/contrib/virtiofsd/fuse_kernel.h b/contrib/virtiofsd/fuse_kernel.h
> > > index ce46046a4f..093cacff02 100644
> > > --- a/contrib/virtiofsd/fuse_kernel.h
> > > +++ b/contrib/virtiofsd/fuse_kernel.h
> > > @@ -830,9 +830,14 @@ struct fuse_setupmapping_out {
> > >          uint64_t        len[FUSE_SETUPMAPPING_ENTRIES];
> > >  };
> > >
> > > -struct fuse_removemapping_in {
> > > +struct fuse_removemapping_in_header {
> > >          /* An already open handle */
> > > -     uint64_t        fh;
> > > +        uint64_t        fh;
> > > +        /* number of fuse_removemapping_in follows */
> > > +        unsigned        num;
> >
> > I think all fields in fuse structures are fixed length - e.g. uint32_t
> > or uint64_t.
> >
> > > +};
> > > +
> > > +struct fuse_removemapping_in {
> > >          /* Offset into the dax to start the unmapping */
> > >          uint64_t        moffset;
> > >          /* Length of mapping required */
> >
> > Miklos: Does this make sense for a fuse structure? It's that header
> > followed by 'num' of fuse_removemapping_in.
> 
> There's one example of that already: fuse_batch_forget_in followed by
> 'count' number of fuse_forget_one.

OK, it would be great to follow the same naming pattern for this.

Dave

> Thanks,
> Miklos
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK


  reply	other threads:[~2019-05-22 11:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 14:41 [Virtio-fs] [PATCH] virtiofsd: make FUSE_REMOVEMAPPING support multiple entries Peng Tao
2019-05-22 11:26 ` Dr. David Alan Gilbert
2019-05-22 11:31   ` Miklos Szeredi
2019-05-22 11:38     ` Dr. David Alan Gilbert [this message]
2019-05-24  4:21   ` Tao Peng

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=20190522113832.GD2666@work-vm \
    --to=dgilbert@redhat.com \
    --cc=mszeredi@redhat.com \
    --cc=tao.peng@linux.alibaba.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.