All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengnan Chang <changfengnan@vivo.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] fuse: use newer inode info when writeback cache is enabled
Date: Tue, 10 Aug 2021 09:41:40 +0800	[thread overview]
Message-ID: <c5982115-e62c-908c-8aac-011ca682f193@vivo.com> (raw)
In-Reply-To: <CAJfpeguErrcKc7CKjnp-uM9VMyUjrtjipv7KGSu5xeY9joOQxQ@mail.gmail.com>

Remove cache=always still have this problem, this problem is related 
about FUSE_CAP_WRITEBACK_CACHE.

On 2021/8/6 20:20, Miklos Szeredi wrote:
> On Thu, 24 Jun 2021 at 09:42, Fengnan Chang <changfengnan@vivo.com> wrote:
>>
>> Hi Miklos:
>>
>> Thank you for the information, I have been able to reproduce the problem.
>>
>> The new version of the patch as below. Previous fsx test is pass now.
>> Need do more test, Can you help to test new patch? or send me your test
>> case, I will test this.
>>
>> Here is my test case, and is the problem this patch is trying to solve.
>> Case A:
>> mkdir /tmp/test
>> passthrough_ll -ocache=always,writeback /mnt/test/
>> echo "11111" > /tmp/test/fsx
>> ls -l /mnt/test/tmp/test/
>> echo "2222" >> /tmp/test/fsx
>> ls -l /mnt/test/tmp/test/
>>
>> Case B:
>> mkdir /tmp/test
>> passthrough_ll -ocache=always,writeback /mnt/test/
>> passthrough_ll -ocache=always,writeback /mnt/test2/
>> echo "11111" > /tmp/test/fsx
>> ls -l /mnt/test/tmp/test/
>> ls -l /mnt/test2/tmp/test/
>> echo "222" >> /mnt/test/tmp/test/fsx
>> ls -l /mnt/test/tmp/test/
>> ls -l /mnt/test2/tmp/test/
> 
> Both these testcases have the "cache=always" option, which means:
> cached values (both data and metadata) are always valid; i.e. changes
> will be made only through this client and not through some other
> channel (like the backing filesystem or another instance).
> 
> Why is "cache=always" used?
> 
> Thanks,
> Miklos
> 

  reply	other threads:[~2021-08-10  1:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30  8:50 [PATCH v2] fuse: use newer inode info when writeback cache is enabled Fengnan Chang
2021-05-07 10:04 ` Fengnan Chang
2021-06-22  7:59 ` Miklos Szeredi
2021-06-22 12:25   ` Fengnan Chang
2021-06-22 15:19     ` Miklos Szeredi
2021-06-24  7:42       ` Fengnan Chang
2021-06-25  3:42         ` Fengnan Chang
2021-08-06 12:20         ` Miklos Szeredi
2021-08-10  1:41           ` Fengnan Chang [this message]
2021-08-16  2:48             ` Peng Tao
2021-05-07 10:09 changfengnan
2021-05-11 11:21 ` 答复: " changfengnan
2021-05-12 12:33   ` Miklos Szeredi

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=c5982115-e62c-908c-8aac-011ca682f193@vivo.com \
    --to=changfengnan@vivo.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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.