From: Mel Gorman <email@example.com> To: Andrew Morton <firstname.lastname@example.org> Cc: Thomas Gleixner <email@example.com>, Ingo Molnar <firstname.lastname@example.org>, Vlastimil Babka <email@example.com>, Hugh Dickins <firstname.lastname@example.org>, Linux-MM <email@example.com>, Linux-RT-Users <firstname.lastname@example.org>, LKML <email@example.com>, Mel Gorman <firstname.lastname@example.org> Subject: [PATCH 0/2] Protect vmstats on PREEMPT_RT Date: Fri, 23 Jul 2021 11:00:32 +0100 [thread overview] Message-ID: <email@example.com> (raw) When adding local_lock support to mm/page_alloc.c and reducing the overhead of vmstats in general, I wondered how vmstats could be safe on PREEMPT_RT as it partially relies on interrupts being disabled for the stats that must be accurate for correctness. As it turns out, the preempt-rt tree already encountered the same problem. This series protects just the primary counters. While there is another vmstat-related patch, it is related to memcg getting using local_lock and I have not fully considered those patches and whether they are ok as-is or need modification but this series makes a start. Patch 1 is authored by Thomas (cc'd) and has not being altered. Patch 2 is authored by Ingo (cc'd) but I modified what he implemented for reasons explained in the changelog. This is specific to PREEMPT_RT which cannot be enabled on mainline yet and should have no impact on !PREEMPT_RT kernels. include/linux/preempt.h | 18 +++++++++++++++++- mm/vmstat.c | 12 ++++++++++++ 2 files changed, 29 insertions(+), 1 deletion(-) -- 2.26.2
next reply other threads:[~2021-07-23 10:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-23 10:00 Mel Gorman [this message] 2021-07-23 10:00 ` [PATCH 1/2] preempt: Provide preempt_*_(no)rt variants Mel Gorman 2021-07-23 10:00 ` [PATCH 2/2] mm/vmstat: Protect per cpu variables with preempt disable on RT Mel Gorman 2021-08-03 23:54 ` Thomas Gleixner 2021-08-04 9:54 ` Mel Gorman 2021-08-04 13:42 ` Vlastimil Babka 2021-08-04 14:23 ` Mel Gorman 2021-08-05 12:56 ` Thomas Gleixner 2021-08-05 14:04 ` Mel Gorman 2021-08-05 15:42 ` Thomas Gleixner 2021-08-05 18:47 ` Daniel Vacek
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH 0/2] Protect vmstats on PREEMPT_RT' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).