From: David Howells <dhowells@redhat.com>
To: =?utf-8?Q?Aur=C3=A9lien?= Aptel <aaptel@suse.com>
Cc: dhowells@redhat.com, Steve French <smfrench@gmail.com>,
Xiaoli Feng <xifeng@redhat.com>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: FS-Cache for cifs
Date: Thu, 13 Aug 2020 16:32:14 +0100 [thread overview]
Message-ID: <322210.1597332734@warthog.procyon.org.uk> (raw)
In-Reply-To: <87tux64mns.fsf@suse.com>
Aurélien Aptel <aaptel@suse.com> wrote:
> Is there an overview document somewhere that describe what fscache does?
> We are seeing some warnings about duplicated entries in some scenarios
> but I'd like to understand better what it does before changing what goes
> in the key.
Documentation/filesystems/caching/* in the kernel.
David
prev parent reply other threads:[~2020-08-13 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1097808468.45751159.1597108422888.JavaMail.zimbra@redhat.com>
2020-08-11 1:25 ` FS-Cache for cifs Xiaoli Feng
2020-08-11 1:51 ` Steve French
[not found] ` <CAH2r5mvkUsp29RPEOmDRra+0GQn_AH1QhabKkEdQZafOLBCv9w@mail.gmail.com>
2020-08-12 5:15 ` Xiaoli Feng
2020-08-12 16:21 ` David Wysochanski
2020-08-13 14:59 ` Aurélien Aptel
2020-08-13 15:32 ` David Howells [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=322210.1597332734@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=xifeng@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox