linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shyam Prasad N <nspmangalore@gmail.com>
To: David Howells <dhowells@redhat.com>,
	CIFS <linux-cifs@vger.kernel.org>,
	Steve French <smfrench@gmail.com>
Subject: fscache metadata query
Date: Wed, 9 Jun 2021 20:13:23 +0530	[thread overview]
Message-ID: <CANT5p=prtZ5ZZGSrFFb4sOc_+-tytDpL1s4VzMnsk1vGq2d5Jg@mail.gmail.com> (raw)

Hi David,

I was exploring the cifs.ko implementation of fscache recently for a
customer use case.
For this use case, I felt that it would be quite useful to obtain info
about what data (pages) are currently cached by fscache. Is there
already a mechanism to be able to get this information? Or is
something planned on similar lines?

Even if fscache provides netfs a way to provide callback functions
which can get called when older data is culled by fscache, the netfs
can maintain this metadata internally.

More thoughts?

--
Regards,
Shyam

                 reply	other threads:[~2021-06-09 14:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CANT5p=prtZ5ZZGSrFFb4sOc_+-tytDpL1s4VzMnsk1vGq2d5Jg@mail.gmail.com' \
    --to=nspmangalore@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.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;
as well as URLs for NNTP newsgroup(s).