From: Andrew Morton <akpm@linux-foundation.org>
To: Shakeel Butt <shakeelb@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: convert mm's rss stats into percpu_counter
Date: Mon, 24 Oct 2022 15:30:22 -0700 [thread overview]
Message-ID: <20221024153022.1b81a182eac44797b40bfda1@linux-foundation.org> (raw)
In-Reply-To: <20221024052841.3291983-1-shakeelb@google.com>
On Mon, 24 Oct 2022 05:28:41 +0000 Shakeel Butt <shakeelb@google.com> wrote:
> Currently mm_struct maintains rss_stats which are updated on page fault
> and the unmapping codepaths. For page fault codepath the updates are
> cached per thread with the batch of TASK_RSS_EVENTS_THRESH which is 64.
> The reason for caching is performance for multithreaded applications
> otherwise the rss_stats updates may become hotspot for such
> applications.
>
> However this optimization comes with the cost of error margin in the rss
> stats. The rss_stats for applications with large number of threads can
> be very skewed. At worst the error margin is (nr_threads * 64) and we
> have a lot of applications with 100s of threads, so the error margin can
> be very high. Internally we had to reduce TASK_RSS_EVENTS_THRESH to 32.
>
> Recently we started seeing the unbounded errors for rss_stats for
> specific applications which use TCP rx0cp. It seems like
> vm_insert_pages() codepath does not sync rss_stats at all.
>
> This patch converts the rss_stats into percpu_counter to convert the
> error margin from (nr_threads * 64) to approximately (nr_cpus ^ 2).
Confused. The max error should be O(nr_cpus)?
> However this conversion enable us to get the accurate stats for
> situations where accuracy is more important than the cpu cost. Though
> this patch does not make such tradeoffs.
Curiousity. Can you expand on the final sentence here?
> 8 files changed, 40 insertions(+), 107 deletions(-)
There's that, too.
next prev parent reply other threads:[~2022-10-24 22:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 5:28 Shakeel Butt
2022-10-24 22:30 ` Andrew Morton [this message]
2022-10-24 23:14 ` Shakeel Butt
[not found] ` <CGME20221102210957eucas1p2915f88d8b923ccf79f0e8770d208a1bd@eucas1p2.samsung.com>
2022-11-02 21:09 ` Marek Szyprowski
2022-11-03 17:14 ` Shakeel Butt
2022-11-03 23:02 ` Marek Szyprowski
2022-11-04 0:18 ` Shakeel Butt
2022-11-04 23:05 ` Andrew Morton
2022-11-04 23:15 ` Shakeel Butt
2023-06-08 11:14 ` Jan Kara
2023-06-08 16:33 ` Yu Zhao
2023-06-08 17:37 ` Shakeel Butt
2023-06-08 18:07 ` Jan Kara
2023-06-08 19:10 ` Dennis Zhou
2023-06-08 19:36 ` Shakeel Butt
2023-06-14 8:37 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=20221024153022.1b81a182eac44797b40bfda1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shakeelb@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