From: Vlastimil Babka <vbabka@suse.cz>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Michal Hocko <mhocko@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
david@redhat.com, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, rppt@kernel.org, surenb@google.com,
donettom@linux.ibm.com, aboorvad@linux.ibm.com, sj@kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: fix the inaccurate memory statistics issue for users
Date: Wed, 4 Jun 2025 15:46:15 +0200 [thread overview]
Message-ID: <1aa7c368-c37f-4b00-876c-dcf51a523c42@suse.cz> (raw)
In-Reply-To: <250ec733-8b2d-4c56-858c-6aada9544a55@linux.alibaba.com>
On 6/4/25 14:46, Baolin Wang wrote:
>> Baolin, please run stress-ng command that stresses minor anon page
>> faults in multiple threads and then run multiple bash scripts which cat
>> /proc/pidof(stress-ng)/status. That should be how much the stress-ng
>> process is impacted by the parallel status readers versus without them.
>
> Sure. Thanks Shakeel. I run the stress-ng with the 'stress-ng --fault 32
> --perf -t 1m' command, while simultaneously running the following
> scripts to read the /proc/pidof(stress-ng)/status for each thread.
How many of those scripts?
> From the following data, I did not observe any obvious impact of this
> patch on the stress-ng tests when repeatedly reading the
> /proc/pidof(stress-ng)/status.
>
> w/o patch
> stress-ng: info: [6891] 3,993,235,331,584 CPU Cycles
> 59.767 B/sec
> stress-ng: info: [6891] 1,472,101,565,760 Instructions
> 22.033 B/sec (0.369 instr. per cycle)
> stress-ng: info: [6891] 36,287,456 Page Faults Total
> 0.543 M/sec
> stress-ng: info: [6891] 36,287,456 Page Faults Minor
> 0.543 M/sec
>
> w/ patch
> stress-ng: info: [6872] 4,018,592,975,968 CPU Cycles
> 60.177 B/sec
> stress-ng: info: [6872] 1,484,856,150,976 Instructions
> 22.235 B/sec (0.369 instr. per cycle)
> stress-ng: info: [6872] 36,547,456 Page Faults Total
> 0.547 M/sec
> stress-ng: info: [6872] 36,547,456 Page Faults Minor
> 0.547 M/sec
>
> =========================
> #!/bin/bash
>
> # Get the PIDs of stress-ng processes
> PIDS=$(pgrep stress-ng)
>
> # Loop through each PID and monitor /proc/[pid]/status
> for PID in $PIDS; do
> while true; do
> cat /proc/$PID/status
> usleep 100000
Hm but this limits the reading to 10 per second? If we want to simulate an
adversary process, it should be without the sleeps I think?
> done &
> done
next prev parent reply other threads:[~2025-06-04 13:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 1:59 Baolin Wang
2025-05-30 3:53 ` Andrew Morton
2025-05-30 13:39 ` Michal Hocko
2025-05-30 23:00 ` Andrew Morton
2025-06-03 8:08 ` Baolin Wang
2025-06-03 8:15 ` Michal Hocko
2025-06-03 8:32 ` Baolin Wang
2025-06-03 10:28 ` Michal Hocko
2025-06-03 14:22 ` Baolin Wang
2025-06-03 14:48 ` Michal Hocko
2025-06-03 17:29 ` Shakeel Butt
2025-06-04 12:46 ` Baolin Wang
2025-06-04 13:46 ` Vlastimil Babka [this message]
2025-06-04 14:16 ` Baolin Wang
2025-06-04 14:27 ` Vlastimil Babka
2025-06-04 16:54 ` Shakeel Butt
2025-06-05 0:48 ` Baolin Wang
2025-06-05 6:32 ` Michal Hocko
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=1aa7c368-c37f-4b00-876c-dcf51a523c42@suse.cz \
--to=vbabka@suse.cz \
--cc=Liam.Howlett@oracle.com \
--cc=aboorvad@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--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=shakeel.butt@linux.dev \
--cc=sj@kernel.org \
--cc=surenb@google.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