From: Michael Ellerman <mpe@ellerman.id.au>
To: Zhen Lei <thunder.leizhen@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-api <linux-api@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michal Hocko <mhocko@suse.com>, linux-mm <linux-mm@kvack.org>
Cc: Tianhong Ding <dingtianhong@huawei.com>,
Hanjun Guo <guohanjun@huawei.com>,
Libin <huawei.libin@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH v2 1/1] mm: only dispaly online cpus of the numa node
Date: Tue, 03 Oct 2017 12:22:44 +1100 [thread overview]
Message-ID: <8760bxdnyz.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1506678805-15392-2-git-send-email-thunder.leizhen@huawei.com>
Zhen Lei <thunder.leizhen@huawei.com> writes:
> When I executed numactl -H(which read /sys/devices/system/node/nodeX/cpumap
> and display cpumask_of_node for each node), but I got different result on
> X86 and arm64. For each numa node, the former only displayed online CPUs,
> and the latter displayed all possible CPUs. Unfortunately, both Linux
> documentation and numactl manual have not described it clear.
FWIW powerpc happens to implement the x86 behaviour, online CPUs only.
cheers
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-10-03 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 9:53 [PATCH v2 0/1] " Zhen Lei
2017-09-29 9:53 ` [PATCH v2 1/1] " Zhen Lei
2017-10-02 10:38 ` Will Deacon
2017-10-02 21:54 ` Andrew Morton
2017-10-03 13:47 ` Will Deacon
2017-10-03 13:56 ` Michal Hocko
2017-10-09 6:06 ` Leizhen (ThunderTown)
2017-10-03 1:22 ` Michael Ellerman [this message]
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=8760bxdnyz.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=catalin.marinas@arm.com \
--cc=dingtianhong@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=guohanjun@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=thunder.leizhen@huawei.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will.deacon@arm.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