From: Dave Chinner <david@fromorbit.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 00/10] shrinker debugging, .to_text() report (resend)
Date: Wed, 28 Aug 2024 11:51:34 +1000 [thread overview]
Message-ID: <Zs6CpsYtsL4mtoSN@dread.disaster.area> (raw)
In-Reply-To: <20240824191020.3170516-1-kent.overstreet@linux.dev>
On Sat, Aug 24, 2024 at 03:10:07PM -0400, Kent Overstreet wrote:
> recently new OOMs have been cropping up, and reclaim is implicated, so
> I've had to dust off these patches.
>
> nothing significant has changed since the last time I posted, and they
> have been valuable - Dave, think we can get them in?
You need to describe what this does. What does the output look like?
Where does it go (console, dmesg, etc). When is it called, etc.
Links to previous review threads so people can get back up to speed
on what was discussed last time and determine whether issues raised
were solved. A changelog since the last posting is helpful, too...
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2024-08-28 1:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 19:10 Kent Overstreet
2024-08-24 19:10 ` [PATCH 01/10] seq_buf: seq_buf_human_readable_u64() Kent Overstreet
2024-08-24 19:10 ` [PATCH 02/10] mm: shrinker: Add a .to_text() method for shrinkers Kent Overstreet
2024-08-26 3:01 ` Qi Zheng
2024-08-26 3:04 ` Kent Overstreet
2024-08-26 3:10 ` Qi Zheng
2024-08-26 3:32 ` Kent Overstreet
2024-08-28 3:32 ` Dave Chinner
2024-08-24 19:10 ` [PATCH 03/10] mm: shrinker: Add new stats for .to_text() Kent Overstreet
2024-08-28 2:36 ` Dave Chinner
2024-08-28 2:42 ` Kent Overstreet
2024-08-24 19:10 ` [PATCH 04/10] mm: Centralize & improve oom reporting in show_mem.c Kent Overstreet
2024-08-24 19:10 ` [PATCH 05/10] mm: shrinker: Add shrinker_to_text() to debugfs interface Kent Overstreet
2024-08-24 19:10 ` [PATCH 06/10] bcachefs: shrinker.to_text() methods Kent Overstreet
2024-08-24 19:10 ` [PATCH 07/10] percpu: per_cpu_sum() Kent Overstreet
2024-08-24 19:10 ` [PATCH 08/10] fs: Add super_block->s_inodes_nr Kent Overstreet
2024-08-24 19:10 ` [PATCH 09/10] fs/dcache: Add per-sb accounting for nr dentries Kent Overstreet
2024-08-24 19:10 ` [PATCH 10/10] fs: super_cache_to_text() Kent Overstreet
2024-08-28 3:43 ` Dave Chinner
2024-08-28 1:51 ` Dave Chinner [this message]
2024-08-28 2:23 ` [PATCH 00/10] shrinker debugging, .to_text() report (resend) Kent Overstreet
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=Zs6CpsYtsL4mtoSN@dread.disaster.area \
--to=david@fromorbit.com \
--cc=kent.overstreet@linux.dev \
--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