From: Vlastimil Babka <vbabka@suse.cz>
To: Dennis Zhou <dennis@kernel.org>
Cc: Baoquan He <bhe@redhat.com>, kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
42.hyeyoo@gmail.com
Subject: Re: [linux-next:master 5002/7443] include/linux/compiler_types.h:357:45: error: call to '__compiletime_assert_474' declared with attribute error: BUILD_BUG_ON failed: PERCPU_DYNAMIC_EARLY_SIZE < NR_KMALLOC_TYPES * KMALLOC_SHIFT_HIGH * sizeof(struct kmem_cache_cpu)
Date: Mon, 21 Nov 2022 10:22:04 +0100 [thread overview]
Message-ID: <5bb911d7-bef2-b8ae-147b-d7febf5cbd91@suse.cz> (raw)
In-Reply-To: <Y3fYKnMZ0d/jtoKN@fedora>
On 11/18/22 20:08, Dennis Zhou wrote:
> On Fri, Nov 18, 2022 at 10:49:43AM +0100, Vlastimil Babka wrote:
>> >
>> > I think I might be overindexing on the out of tree modifications here.
>> > Currently, I think it's clear how modifying PERCPU_DYNAMIC_RESERVE
>> > affects the system with the lower bound being dictated by
>> > PERCPU_DYNAMIC_EARLY_SIZE. If we bump PERCPU_DYNAMIC_EARLY_SIZE, it's
>> > not inherently obvious you can drop that value lower depending on your
>> > system config.
>> >
>> > Ultimately, it is only a few pages, so is saving it that big of a deal
>> > today? Likely not, just a bit wasteful to potentially orphan a few extra
>> > pages unnecessarily.
>> >
>> > Let's just fix this now and I can massage this in the future if anything
>> > comes up. I appreciate you taking the time to have this discussion with
>> > me.
>> >
>> > Vlastimil, can you please pick up this fix.
>>
>> Sorry, got a bit lost, so do you mean the original uncoditional bump, or the
>> modification with BITS_PER_LONG > 32 (or PAGE_SHIFT > 12)?
>>
>
> No I've made this more complicated than necessary. Please pick up the
> original unconditional bump.
>
> There's a small chance you'll see a merge conflict in my percpu#for-6.2
> tree:
> d667c94962c1 ("mm/percpu: remove unused PERCPU_DYNAMIC_EARLY_SLOTS")
Thanks, picked up.
> Thanks,
> Dennis
>
>> > Acked-by: Dennis Zhou <dennis@kernel.org>
>> >
>> > Thanks,
>> > Dennis
next prev parent reply other threads:[~2022-11-21 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 20:15 kernel test robot
2022-11-12 0:45 ` Baoquan He
2022-11-14 7:44 ` Baoquan He
2022-11-14 17:58 ` Vlastimil Babka
2022-11-15 4:13 ` Dennis Zhou
2022-11-15 9:08 ` Baoquan He
2022-11-15 20:00 ` Dennis Zhou
2022-11-16 11:32 ` Baoquan He
2022-11-17 19:23 ` Dennis Zhou
2022-11-18 3:40 ` Baoquan He
2022-11-18 9:49 ` Vlastimil Babka
2022-11-18 19:08 ` Dennis Zhou
2022-11-21 9:22 ` Vlastimil Babka [this message]
2022-11-16 12:49 ` Hyeonggon Yoo
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=5bb911d7-bef2-b8ae-147b-d7febf5cbd91@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=bhe@redhat.com \
--cc=dennis@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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