From: Vlastimil Babka <vbabka@suse.cz>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Cc: Arnd Bergmann <arnd@kernel.org>, Christoph Lameter <cl@linux.com>,
David Rientjes <rientjes@google.com>,
Dennis Zhou <dennis@kernel.org>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Pekka Enberg <penberg@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Tejun Heo <tj@kernel.org>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] mm: percpu: Increase PERCPU_DYNAMIC_SIZE_SHIFT on certain builds.
Date: Mon, 7 Oct 2024 16:34:59 +0200 [thread overview]
Message-ID: <1f958b18-331c-4290-a575-a9271162c361@suse.cz> (raw)
In-Reply-To: <20241007143049.gyMpEu89@linutronix.de>
On 10/7/24 4:30 PM, Sebastian Andrzej Siewior wrote:
> Arnd reported a build failure due to the BUILD_BUG_ON() statement in
> alloc_kmem_cache_cpus(). The test
>
> PERCPU_DYNAMIC_EARLY_SIZE < NR_KMALLOC_TYPES * KMALLOC_SHIFT_HIGH * sizeof(struct kmem_cache_cpu)
>
> The factors that increase the right side of the equation:
> - PAGE_SIZE > 4KiB increases KMALLOC_SHIFT_HIGH
> - For the local_lock_t in kmem_cache_cpu:
> - PREEMPT_RT adds an actual lock.
> - LOCKDEP increases the size of the lock.
> - LOCK_STAT adds additional bytes plus padding to the lockdep
> structure.
>
> The net difference with and without PREEMPT_RT is 88 bytes for the
> lock_lock_t, 96 bytes for kmem_cache_cpu due to additional padding.
> This is enough to exceed the 80KiB limit with 16KiB page size - the 8KiB
> page size is fine.
>
> Increase PERCPU_DYNAMIC_SIZE_SHIFT to 13 on configs with PAGE_SIZE larger
> than 4KiB and LOCKDEP enabled.
>
> Fixes: d8fccd9ca5f9 ("arm64: Allow to enable PREEMPT_RT.")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202410020326.iaZIteIx-lkp@intel.com/
> Reported-by: Arnd Bergmann <arnd@kernel.org>
> Closes: https://lore.kernel.org/20241004095702.637528-1-arnd@kernel.org
> Acked-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
IIRC Dennis at some point mentioned this will eventually become more
robust as now it's kind of a whack-a-mole? :) But yeah, let's fix in a
way that we can.
Acked-by: Vlastimil Babka <vbabka@suse.cz>
> ---
> include/linux/percpu.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> 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
next prev parent reply other threads:[~2024-10-07 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 14:30 Sebastian Andrzej Siewior
2024-10-07 14:34 ` Vlastimil Babka [this message]
2024-10-13 20:47 ` David Rientjes
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=1f958b18-331c-4290-a575-a9271162c361@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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