From: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] readahead: Add trace points
Date: Wed, 10 Sep 2025 15:56:34 +0200 [thread overview]
Message-ID: <4yz5w6vjnqfidjwss5d4ekprx46u6jityq2b3kq5z7imjj5lpn@de3hz3lglonl> (raw)
In-Reply-To: <20250909145849.5090-2-jack@suse.cz>
On Tue, Sep 09, 2025 at 04:58:50PM +0200, Jan Kara wrote:
> Add a couple of trace points to make debugging readahead logic easier.
>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> include/trace/events/readahead.h | 132 +++++++++++++++++++++++++++++++
> mm/readahead.c | 8 ++
> 2 files changed, 140 insertions(+)
> create mode 100644 include/trace/events/readahead.h
>
> Changes since v1:
> - moved tracepoint from do_page_cache_ra() to page_cache_ra_unbounded() as
> that is a more standard function.
Looks good.
Tested-by: Pankaj Raghav <p.raghav@samsung.com>
--
Pankaj
prev parent reply other threads:[~2025-09-10 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 14:58 Jan Kara
2025-09-10 13:56 ` Pankaj Raghav (Samsung) [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=4yz5w6vjnqfidjwss5d4ekprx46u6jityq2b3kq5z7imjj5lpn@de3hz3lglonl \
--to=kernel@pankajraghav.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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