linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Donet Tom <donettom@linux.ibm.com>,
	akpm@linux-foundation.org, david@redhat.com, shakeelb@google.com
Cc: lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
	vbabka@suse.cz, rppt@kernel.org, surenb@google.com,
	mhocko@suse.com, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] mm: fix the inaccurate memory statistics issue for users
Date: Fri, 23 May 2025 13:47:28 +0800	[thread overview]
Message-ID: <eb7e85f3-90d5-428c-a93a-7e54ade1479c@linux.alibaba.com> (raw)
In-Reply-To: <ac3b8c16-1f2b-4f2f-8bcd-ef8da8544a20@linux.ibm.com>



On 2025/5/23 13:25, Donet Tom wrote:
> 
> On 5/23/25 8:46 AM, Baolin Wang wrote:
>> On some large machines with a high number of CPUs running a 64K kernel,
>> we found that the 'RES' field is always 0 displayed by the top command
>> for some processes, which will cause a lot of confusion for users.
>>
>>      PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     
>> TIME+ COMMAND
>>   875525 root      20   0   12480      0      0 R   0.3   0.0   
>> 0:00.08 top
>>        1 root      20   0  172800      0      0 S   0.0   0.0   
>> 0:04.52 systemd
>>
>> The main reason is that the batch size of the percpu counter is quite 
>> large
>> on these machines, caching a significant percpu value, since 
>> converting mm's
>> rss stats into percpu_counter by commit f1a7941243c1 ("mm: convert 
>> mm's rss
>> stats into percpu_counter"). Intuitively, the batch number should be 
>> optimized,
>> but on some paths, performance may take precedence over statistical 
>> accuracy.
>> Therefore, introducing a new interface to add the percpu statistical 
>> count
>> and display it to users, which can remove the confusion. In addition, 
>> this
>> change is not expected to be on a performance-critical path, so the 
>> modification
>> should be acceptable.
>>
>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>> ---
>>   fs/proc/task_mmu.c | 14 +++++++-------
>>   include/linux/mm.h |  5 +++++
>>   2 files changed, 12 insertions(+), 7 deletions(-)
>>
>> diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
>> index b9e4fbbdf6e6..f629e6526935 100644
>> --- a/fs/proc/task_mmu.c
>> +++ b/fs/proc/task_mmu.c
>> @@ -36,9 +36,9 @@ void task_mem(struct seq_file *m, struct mm_struct *mm)
>>       unsigned long text, lib, swap, anon, file, shmem;
>>       unsigned long hiwater_vm, total_vm, hiwater_rss, total_rss;
>> -    anon = get_mm_counter(mm, MM_ANONPAGES);
>> -    file = get_mm_counter(mm, MM_FILEPAGES);
>> -    shmem = get_mm_counter(mm, MM_SHMEMPAGES);
>> +    anon = get_mm_counter_sum(mm, MM_ANONPAGES);
> 
> 
> Hi Baolin Wang,
> 
> We also observed the same issue where the RSS value in /proc/PID/status
> was 0 on machines with a high number of CPUs. With this patch, the issue
> got fixedl

Yes, we also observed this issue.

> Rss value without this patch
> ----------------------------
>   # cat /proc/87406/status
> .....
> VmRSS:           0 kB
> RssAnon:           0 kB
> RssFile:           0 k
> 
> 
> Rss values with this patch
> --------------------------
>   # cat /proc/3055/status
> VmRSS:        2176 kB
> RssAnon:         512 kB
> RssFile:        1664 kB
> RssShmem:           0 kB
> 
> Tested-by Donet Tom <donettom@linux.ibm.com>

Thanks for testing.


  reply	other threads:[~2025-05-23  5:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23  3:16 Baolin Wang
2025-05-23  5:25 ` Donet Tom
2025-05-23  5:47   ` Baolin Wang [this message]
2025-05-23 10:14 ` Aboorva Devarajan
2025-05-24  1:24   ` Baolin Wang
2025-05-30 10:23   ` Michal Hocko
2025-05-23 14:11 ` Shakeel Butt
2025-05-24  1:25   ` Baolin Wang
2025-05-23 17:20 ` SeongJae Park
2025-05-23 17:23   ` SeongJae Park
2025-05-24  1:29     ` Baolin Wang

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=eb7e85f3-90d5-428c-a93a-7e54ade1479c@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=donettom@linux.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=shakeelb@google.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox