From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Dennis Zhou <dennis@kernel.org>
Cc: <akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <tj@kernel.org>,
<gregkh@linuxfoundation.org>, <cl@linux.com>,
<catalin.marinas@arm.com>, <will@kernel.org>,
<tsbogend@alpha.franken.de>, <mpe@ellerman.id.au>,
<benh@kernel.crashing.org>, <paulus@samba.org>,
<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <davem@davemloft.net>,
<tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <hpa@zytor.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-ia64@vger.kernel.org>, <linux-mips@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>,
<linux-riscv@lists.infradead.org>, <sparclinux@vger.kernel.org>,
<x86@kernel.org>
Subject: Re: [PATCH RFC 1/4] mm: percpu: Generalize percpu related config
Date: Tue, 30 Nov 2021 14:22:07 +0800 [thread overview]
Message-ID: <35e4a4cb-29f2-2de6-6350-1358d4968a54@huawei.com> (raw)
In-Reply-To: <YaVV38QSn6LEBKH/@fedora>
On 2021/11/30 6:36, Dennis Zhou wrote:
> Hello,
>
> On Sun, Nov 21, 2021 at 05:35:54PM +0800, Kefeng Wang wrote:
>> The HAVE_SETUP_PER_CPU_AREA/NEED_PER_CPU_EMBED_FIRST_CHUNK/
>> NEED_PER_CPU_PAGE_FIRST_CHUNK/USE_PERCPU_NUMA_NODE_ID configs,
>> which has duplicate definitions on platforms that subscribe it.
>>
>> Move them into mm, drop these redundant definitions and instead
>> just select it on applicable platforms.
>>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>> arch/arm64/Kconfig | 20 ++++----------------
>> arch/ia64/Kconfig | 9 ++-------
>> arch/mips/Kconfig | 10 ++--------
>> arch/powerpc/Kconfig | 17 ++++-------------
>> arch/riscv/Kconfig | 10 ++--------
>> arch/sparc/Kconfig | 12 +++---------
>> arch/x86/Kconfig | 17 ++++-------------
>> mm/Kconfig | 12 ++++++++++++
>> 8 files changed, 33 insertions(+), 74 deletions(-)
...
>>
> This makes sense and looks good. A series like this is a little tricky.
> The latter patches change the contracts so it'd be easiest to run it
> through my tree. We'd need to get explicit acks from each arch
> maintainer to make sure they're fine with this.
Got it, I will resend without RFC and hope to get ACKs from related arch
maintainers.
>
> Thanks,
> Dennis
> .
next prev parent reply other threads:[~2021-11-30 6:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 9:35 [PATCH RFC 0/4] mm: percpu: Cleanup percpu first chunk funciton Kefeng Wang
2021-11-21 9:35 ` [PATCH RFC 1/4] mm: percpu: Generalize percpu related config Kefeng Wang
2021-11-29 22:36 ` Dennis Zhou
2021-11-30 6:22 ` Kefeng Wang [this message]
2021-12-03 18:54 ` Catalin Marinas
2021-11-21 9:35 ` [PATCH RFC 2/4] mm: percpu: Add pcpu_fc_cpu_to_node_fn_t typedef Kefeng Wang
2021-11-29 22:40 ` Dennis Zhou
2021-11-30 6:22 ` Kefeng Wang
2021-11-21 9:35 ` [PATCH RFC 3/4] mm: percpu: Add generic pcpu_fc_alloc/free funciton Kefeng Wang
2021-11-29 22:45 ` Dennis Zhou
2021-11-30 6:27 ` Kefeng Wang
2021-11-21 9:35 ` [PATCH RFC 4/4] mm: percpu: Add generic pcpu_populate_pte() function Kefeng Wang
2021-11-29 22:49 ` Dennis Zhou
2021-11-30 6:42 ` Kefeng Wang
2021-11-29 2:51 ` [PATCH RFC 0/4] mm: percpu: Cleanup percpu first chunk funciton Kefeng Wang
2021-11-29 2:54 ` Dennis Zhou
2021-11-29 3:06 ` Kefeng Wang
2021-11-29 22:55 ` Dennis Zhou
2021-11-30 6:53 ` Kefeng Wang
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=35e4a4cb-29f2-2de6-6350-1358d4968a54@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dennis@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulus@samba.org \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=will@kernel.org \
--cc=x86@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