All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Tao <tao.peng@linux.alibaba.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: virtio-fs@redhat.com
Subject: Re: [Virtio-fs] [PATCH-v3 0/1] virtiofs: FUSE_REMOVEMAPPING remove multiple entries in one call
Date: Thu, 6 Jun 2019 14:51:53 +0800	[thread overview]
Message-ID: <3df1985d-7ba8-c435-d6c3-24c16d61124f@linux.alibaba.com> (raw)
In-Reply-To: <20190605203016.GC22236@redhat.com>



On 2019/6/6 04:30, Vivek Goyal wrote:
> Hi Peng Tao,
> 
> I have squashed this patch and forget request wait patches into existing
> pathces and pushed latest patches here.
> 
> https://github.com/rhvgoyal/linux/commits/virtio-fs-dev-5.1
> 
> Please give it a try.
Both look good and work as expected. Thanks!

Cheers,
Tao

> 
> I have made more function name changes into existing patches. There were
> so many functions with name fuse_dax_free* that I was finding it hard
> to remember which function is doing what.
> 
> Thanks
> Vivek
> 
> On Wed, Jun 05, 2019 at 11:02:32AM +0800, Peng Tao wrote:
>> Hi Vivek,
>>
>> This works with corresponding qemu virtiofsd patch:
>> "[PATCH-v3] virtiofsd: make FUSE_REMOVEMAPPING support multiple entries".
>>
>> v1-v2: make fuse_removemapping_in count fuse_removemapping_one
>> v2->v3:
>> 1. fold in Vivek's cleanup and rename all forget_one to remove_one
>> 2. assert dmap->list is not used by anyone when adding to temporary list
>> 3. list_del() dmap->list when removing it from to_remove list
>>
>> Please add your SOB line as I don't see it with your cleanup and thus
>> did not add it to the patch when folding your change.
>>
>> Thanks,
>> Tao
>>
>> Peng Tao (1):
>>    virtiofs: FUSE_REMOVEMAPPING remove multiple entries in one call
>>
>>   fs/fuse/file.c            | 205 +++++++++++++++++++++++++++-----------
>>   fs/fuse/fuse_i.h          |   6 +-
>>   fs/fuse/inode.c           |   2 +-
>>   include/uapi/linux/fuse.h |   7 ++
>>   4 files changed, 160 insertions(+), 60 deletions(-)
>>
>> -- 
>> 2.17.1
>>

-- 
Into something rich and strange.


      reply	other threads:[~2019-06-06  6:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05  3:02 [Virtio-fs] [PATCH-v3 0/1] virtiofs: FUSE_REMOVEMAPPING remove multiple entries in one call Peng Tao
2019-06-05  3:02 ` [Virtio-fs] [PATCH] " Peng Tao
2019-06-05 18:06   ` Liu Bo
2019-06-05 18:35     ` Vivek Goyal
2019-06-05 18:50       ` Liu Bo
2019-06-05 20:30 ` [Virtio-fs] [PATCH-v3 0/1] " Vivek Goyal
2019-06-06  6:51   ` Peng Tao [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=3df1985d-7ba8-c435-d6c3-24c16d61124f@linux.alibaba.com \
    --to=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.