All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Liu <ye.liu@linux.dev>
To: David Hildenbrand <david@redhat.com>, Michal Hocko <mhocko@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ye Liu <liuye@kylinos.cn>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmstat: add header line to /proc/buddyinfo output
Date: Thu, 18 Sep 2025 16:31:22 +0800	[thread overview]
Message-ID: <6d6e2e33-c221-4ab8-a29b-3d14fb1a592c@linux.dev> (raw)
In-Reply-To: <780aa9d6-a85c-4050-820e-c0ca9f5bb658@redhat.com>



在 2025/9/18 16:16, David Hildenbrand 写道:
> On 18.09.25 10:11, Ye Liu wrote:
>>
>>
>> 在 2025/9/18 15:29, Michal Hocko 写道:
>>> On Thu 18-09-25 15:17:40, Ye Liu wrote:
>>>> From: Ye Liu <liuye@kylinos.cn>
>>>>
>>>> Add a header line to /proc/buddyinfo that shows the order numbers
>>>> for better readability and clarity.
>>>>
>>>> Before:
>>>> Node 0, zone      DMA      0      0      0      0      0      0      0 ...
>>>> Node 0, zone    DMA32      5      8      6      6      7      5      8 ...
>>>> Node 0, zone   Normal   1113    351    138     65     38     31     25 ...
>>>>
>>>> After:
>>>> Free pages per order       0      1      2      3      4      5      6 ...
>>>> Node 0, zone      DMA      0      0      0      0      0      0      0 ...
>>>> Node 0, zone    DMA32      5      8      6      6      7      5      8 ...
>>>> Node 0, zone   Normal   1113    351    138     65     38     31     25 ...
>>>
>>> Why is this needed? And have you considered tha this might break
>>> existing parsers of the file?
>>>
>>
>> Thanks for the review.
>>
>> The reason for this change is simply to make /proc/buddyinfo self-describing.
>> Right now you have to know which column is which order; with a header it’s
>> obvious. This is similar to what /proc/pagetypeinfo already does, e.g.:
>>
>>    Page block order: 9
>>    Pages per block: 512
>>
>>    Free pages count per migrate type at order   0 1 2 3 ...
>>    Node 0, zone DMA, type Unmovable             0 0 0 ...
>>
>> Regarding existing parsers: the patch does not change any of the existing
>> “Node … zone …” lines, it only adds a single header line before them. Most
>> parsers match “Node” lines and ignore everything else, so the risk should be
>> low. If you know of any existing parser that this would break, please let
>> me know so I can address it.
> 
> What if there is a single one out there that has hardcoded to skip the first line only?

I understand there may be no way to be fully compatible with all existing
parsers. However, /proc/buddyinfo is essentially raw data intended for
human and tool consumption, and parsers are expected to be robust against
format changes.

Adding a '#' prefix to the header would allow most parsers to skip it,
but it still changes the file output and cannot fully guarantee that no
external tool will be affected.                                          


> 

-- 
Thanks,
Ye Liu



  reply	other threads:[~2025-09-18  8:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18  7:17 [PATCH] mm/vmstat: add header line to /proc/buddyinfo output Ye Liu
2025-09-18  7:29 ` Michal Hocko
2025-09-18  8:11   ` Ye Liu
2025-09-18  8:16     ` David Hildenbrand
2025-09-18  8:31       ` Ye Liu [this message]
2025-09-18  8:49         ` Michal Hocko
2025-09-18  9:00           ` Ye Liu
2025-09-18  8:50         ` David Hildenbrand

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=6d6e2e33-c221-4ab8-a29b-3d14fb1a592c@linux.dev \
    --to=ye.liu@linux.dev \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuye@kylinos.cn \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.