From: Michal Hocko <mhocko@kernel.org>
To: Shaokun Zhang <zhangshaokun@hisilicon.com>
Cc: linux-kernel@vger.kernel.org, yuqi jin <jinyuqi@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Paul Burton <paul.burton@mips.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Anshuman Khandual <anshuman.khandual@arm.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v3] lib: optimize cpumask_local_spread()
Date: Fri, 15 Nov 2019 14:36:25 +0100 [thread overview]
Message-ID: <20191115133625.GD29990@dhcp22.suse.cz> (raw)
In-Reply-To: <9af13fea-95a6-30cb-2c0e-770aa649a549@hisilicon.com>
On Fri 15-11-19 17:09:13, Shaokun Zhang wrote:
[...]
> Oh, my mistake, for the previous instance, I don't list all IRQs and
> just choose one IRQ from one NUMA node. You can see that the IRQ
> number is not consistent :-).
> IRQ from 345 to 368 will be bound to CPU cores which are in NUMA node2
> and each IRQ is corresponding to one core.
>
This is quite confusing then. I would suggest providing all IRQ used for
the device with the specific node affinity to see the difference in the
setup.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-11-15 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 1:44 [PATCH v3] lib: optimize cpumask_local_spread() Shaokun Zhang
2019-11-08 3:49 ` Andrew Morton
2019-11-08 5:50 ` Shaokun Zhang
2019-11-08 10:31 ` Michal Hocko
2019-11-11 2:02 ` Shaokun Zhang
2019-11-12 11:56 ` Michal Hocko
2019-11-13 2:46 ` Shaokun Zhang
2019-11-14 14:43 ` Michal Hocko
2019-11-15 9:09 ` Shaokun Zhang
2019-11-15 13:36 ` Michal Hocko [this message]
2019-11-21 8:14 ` Shaokun Zhang
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=20191115133625.GD29990@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=jinyuqi@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=rppt@linux.ibm.com \
--cc=zhangshaokun@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.