public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [RFC] xfs_io: Add cachestat syscall support
Date: Thu, 03 Apr 2025 16:14:56 +0530	[thread overview]
Message-ID: <87v7rl34nr.fsf@gmail.com> (raw)
In-Reply-To: <20250403022829.GA6283@frogsfrogsfrogs>

"Darrick J. Wong" <djwong@kernel.org> writes:

> On Mon, Mar 17, 2025 at 12:15:29AM +0530, Ritesh Harjani (IBM) wrote:
>> This adds -c "cachestat off len" command which uses cachestat() syscall
>> [1]. This can provide following pagecache detail for a file.
>> 
>> - no. of cached pages,
>> - no. of dirty pages,
>> - no. of pages marked for writeback,
>> - no. of evicted pages,
>> - no. of recently evicted pages
>> 
>> [1]: https://lore.kernel.org/all/20230503013608.2431726-3-nphamcs@gmail.com/T/#u
>> 
>> Signed-off-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
>
> Just out of curiosity, is there a manpage change for xfs_io.8 that goes
> with this new subcommand?
>

Looks like I might have missed the man page entry change,...

>> ---
>>  configure.ac          |  1 +
>>  include/builddefs.in  |  1 +
>>  io/Makefile           |  5 +++
>>  io/cachestat.c        | 77 +++++++++++++++++++++++++++++++++++++++++++
>>  io/init.c             |  1 +
>>  io/io.h               |  6 ++++
>>  m4/package_libcdev.m4 | 19 +++++++++++
>>  7 files changed, 110 insertions(+)
>>  create mode 100644 io/cachestat.c

...else we would have seen an entry in man/man8/xfs_io.8 file. 

Since this is taken in for-next, I can submit a separate patch for the
man page entry update.

Thanks for catching it. 

-ritesh

      reply	other threads:[~2025-04-03 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-16 18:45 [RFC] xfs_io: Add cachestat syscall support Ritesh Harjani (IBM)
2025-03-19 10:23 ` Andrey Albershteyn
2025-04-03  2:28 ` Darrick J. Wong
2025-04-03 10:44   ` Ritesh Harjani [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=87v7rl34nr.fsf@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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