From: Shakeel Butt <shakeel.butt@linux.dev>
To: Jianyue Wu <wujianyue000@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, cgroups@vger.kernel.org, hannes@cmpxchg.org,
mhocko@kernel.org, roman.gushchin@linux.dev,
muchun.song@linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm: optimize stat output for 11% sys time reduce
Date: Mon, 12 Jan 2026 16:23:19 -0800 [thread overview]
Message-ID: <uvmqfu2ms7itmfl2bk47yxtbafccscc2hlsw56uq2qy3q6fri3@sl56sf33fvyj> (raw)
In-Reply-To: <7210e5e0-2a93-4d3b-a564-85c0fe117ef5@gmail.com>
On Sun, Jan 11, 2026 at 12:37:45PM +0800, Jianyue Wu wrote:
> On 1/11/2026 7:33 AM, Andrew Morton wrote:
> > On Sat, 10 Jan 2026 12:22:49 +0800 Jianyue Wu <wujianyue000@gmail.com> wrote:
> >
> > > Replace seq_printf/seq_buf_printf with lightweight helpers to avoid
> > > printf parsing in memcg stats output.
> > >
> > I don't understand - your previous email led me to believe that the new
> > BPF interface can be used to address this issue?
>
> Yes, previously I think can directly use BPF interface to speedup. Later I
> think maybe this is still needed, as some platform didn't have BPF installed
> might still use these sysfs files.
>
It seems like this patch adds measurable improvement for the traditional
stat readers. The high performance ones can be switched to the bpf based
interface. So, I see no harm in taking this patch in.
next prev parent reply other threads:[~2026-01-13 0:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 9:37 [PATCH] " Jianyue Wu
2026-01-08 19:10 ` Andrew Morton
2026-01-08 22:49 ` Roman Gushchin
2026-01-08 23:52 ` Jiany Wu
2026-01-08 23:56 ` Jiany Wu
2026-01-10 4:22 ` [PATCH v2] " Jianyue Wu
2026-01-10 23:33 ` Andrew Morton
2026-01-11 4:37 ` Jianyue Wu
2026-01-13 0:23 ` Shakeel Butt [this message]
2026-01-13 0:29 ` Shakeel Butt
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=uvmqfu2ms7itmfl2bk47yxtbafccscc2hlsw56uq2qy3q6fri3@sl56sf33fvyj \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=wujianyue000@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