From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux.com>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
kernel test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Suren Baghdasaryan <surenb@google.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Hou Tao <houtao1@huawei.com>, Jan Kara <jack@suse.cz>,
Jianhui Zhou <912460177@qq.com>,
Yury Norov <yury.norov@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] preempt_rt: increase PERCPU_DYNAMIC_SIZE_SHIFT for slab randomization
Date: Mon, 7 Oct 2024 12:43:48 +0200 [thread overview]
Message-ID: <20241007104348.ImJPXDl9@linutronix.de> (raw)
In-Reply-To: <20241004095702.637528-1-arnd@kernel.org>
On 2024-10-04 09:56:56 [+0000], Arnd Bergmann wrote:
> The problem is the additional size overhead from local_lock in
> struct kmem_cache_cpu. Avoid this by preallocating a larger area.
The worst case would be enabling additionally MEMCG so NR_KMALLOC_TYPES
increases by one. And then we have:
PERCPU_DYNAMIC_EARLY_SIZE < NR_KMALLOC_TYPES * KMALLOC_SHIFT_HIGH * sizeof(struct kmem_cache_cpu));
There is more to it than just RANDOM_KMALLOC_CACHES and PREEMPT_RT.
There is additionally CONFIG_LOCKDEP which increases the size of
local_lock_t further. Plus CONFIG_LOCK_STAT. The last one a kind of bad
in terms of required pad area. Then we have CONFIG_PAGE_SIZE_64KB set
which is the culprit. But 16K_PAGES also fail in this full blown case.
PERCPU_DYNAMIC_EARLY_SIZE < NR_KMALLOC_TYPES * KMALLOC_SHIFT_HIGH * sizeof(struct kmem_cache_cpu));
4KiB 20 << 12 < 19 * (12 + 1) * 288
80KiB < 69.46875
16KiB 20 << 12 < 19 * (14 + 1) * 288
80KiB < 80.15625
64KiB 20 << 12 < 19 * (16 + 1) * 288
80KiB < 90.84375
128KiB 20 << 12 < 19 * (17 + 1) * 288
80KiB < 96.1875
Just disabling CONFIG_LOCK_STAT the 16KiB PAGE_SIZE case works again
(75.703125), the 64KiB still fails (85.796875).
> There is a good chance that there is a better way to address this, this
> version was the first I came up with and I verified that it fixes all of
> the broken configs.
How bad is it, to have PERCPU_DYNAMIC_SIZE_SHIFT unconditionally set to
13? If it is bad could we restrict it with LOCKDEP and PAGE_SIZE > 4KiB?
So maybe something like this:
diff --git a/include/linux/percpu.h b/include/linux/percpu.h
index b6321fc491598..52b5ea663b9f0 100644
--- a/include/linux/percpu.h
+++ b/include/linux/percpu.h
@@ -41,7 +41,11 @@
PCPU_MIN_ALLOC_SHIFT)
#ifdef CONFIG_RANDOM_KMALLOC_CACHES
-#define PERCPU_DYNAMIC_SIZE_SHIFT 12
+# if defined(CONFIG_LOCKDEP) && !defined(CONFIG_PAGE_SIZE_4KB)
+# define PERCPU_DYNAMIC_SIZE_SHIFT 13
+# else
+# define PERCPU_DYNAMIC_SIZE_SHIFT 12
+#endif /* LOCKDEP and PAGE_SIZE > 4KiB */
#else
#define PERCPU_DYNAMIC_SIZE_SHIFT 10
#endif
Sebastian
next prev parent reply other threads:[~2024-10-07 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 9:56 [PATCH] preempt_rt: increase PERCPU_DYNAMIC_SIZE_SHIFT for slab randomization Arnd Bergmann
2024-10-07 10:43 ` Sebastian Andrzej Siewior [this message]
2024-10-07 10:59 ` Arnd Bergmann
2024-10-07 12:22 ` Sebastian Andrzej Siewior
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=20241007104348.ImJPXDl9@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=912460177@qq.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=houtao1@huawei.com \
--cc=jack@suse.cz \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=will@kernel.org \
--cc=yury.norov@gmail.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;
as well as URLs for NNTP newsgroup(s).