linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jianyue Wu <wujianyue000@gmail.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	hannes@cmpxchg.org, mhocko@kernel.org,  roman.gushchin@linux.dev,
	muchun.song@linux.dev, linux-mm@kvack.org,
	 cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	inwardvessel@gmail.com
Subject: Re: [PATCH v3] mm: optimize stat output for 11% sys time reduce
Date: Fri, 23 Jan 2026 09:07:13 +0800	[thread overview]
Message-ID: <CAJxJ_jgGCL8WcyAO1iyF5Eu+6JtcemAPGs-WMFAaHdaM8V3uDA@mail.gmail.com> (raw)
In-Reply-To: <aXKRIOpDrZG37_wz@linux.dev>

On Fri, Jan 23, 2026 at 5:12 AM Shakeel Butt <shakeel.butt@linux.dev> wrote:
>
> On Thu, Jan 22, 2026 at 09:13:51AM -0800, Andrew Morton wrote:
> > On Thu, 22 Jan 2026 19:42:42 +0800 Jianyue Wu <wujianyue000@gmail.com> wrote:
> > So the tl;dr here is "vfprintf() is slow".
> >
> > It's quite a large change, although not a complex one.
> >
> > Do we need to change so much?  Would some subset of these changes
> > provide most of the benefit?
> >
> > It does rather uglify things so there's a risk that helpful people will
> > send "cleanups" which switch back to using *printf*.  Explanatory code
> > comments would help prevent that but we'd need a lot of them.
> >
> > I dunno, what do people think?  Does the benefit justify the change?
>
> It does come with significant benefit but there is no urgency and we can
> definitely decrease the ugliness. JP told me he has some ideas to
> improve this.
>
> Andrew, let's skip this patch for the upcoming merge window and you can
> drop it from mm-tree if it is a burden.
>
Agree. This touches a lot of code and increases complexity, which is a
significant
downside. If there are ideas to improve it, that’d be great.
I’m OK with dropping it for the upcoming merge window, and drop it if
it is a burden.


  reply	other threads:[~2026-01-23  4:47 UTC|newest]

Thread overview: 19+ 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
2026-01-13  0:29         ` Shakeel Butt
2026-01-22 11:42         ` [PATCH v3] " Jianyue Wu
2026-01-22 17:13           ` Andrew Morton
2026-01-22 21:12             ` Shakeel Butt
2026-01-23  1:07               ` Jianyue Wu [this message]
2026-01-23  8:14           ` JP Kobryn
2026-01-23 13:24             ` Jianyue Wu
2026-01-23 15:01             ` [PATCH v4 0/1] mm: memcg: optimize stat output to reduce printf overhead Jianyue Wu
2026-01-23 15:01               ` [PATCH v4 1/1] mm: optimize stat output for 11% sys time reduce Jianyue Wu
2026-01-23 15:06                 ` Jianyue Wu

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=CAJxJ_jgGCL8WcyAO1iyF5Eu+6JtcemAPGs-WMFAaHdaM8V3uDA@mail.gmail.com \
    --to=wujianyue000@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=inwardvessel@gmail.com \
    --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=shakeel.butt@linux.dev \
    /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