From: Peter Zijlstra <peterz@infradead.org>
To: "Nayak, K Prateek" <KPrateek.Nayak@amd.com>
Cc: "aubrey.li@linux.intel.com" <aubrey.li@linux.intel.com>,
"efault@gmx.de" <efault@gmx.de>,
"Shenoy, Gautham Ranjal" <gautham.shenoy@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mgorman@techsingularity.net" <mgorman@techsingularity.net>,
"mingo@kernel.org" <mingo@kernel.org>,
"song.bao.hua@hisilicon.com" <song.bao.hua@hisilicon.com>,
"srikar@linux.vnet.ibm.com" <srikar@linux.vnet.ibm.com>,
"valentin.schneider@arm.com" <valentin.schneider@arm.com>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>
Subject: Re: [PATCH] sched/fair: Consider cpu affinity when allowing NUMA imbalance in find_idlest_group
Date: Wed, 9 Feb 2022 18:20:18 +0100 [thread overview]
Message-ID: <YgP30sLEQfYPsMZE@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <MW2PR12MB237955DEA3F949359A96E031982E9@MW2PR12MB2379.namprd12.prod.outlook.com>
On Wed, Feb 09, 2022 at 03:14:32PM +0000, Nayak, K Prateek wrote:
> [AMD Official Use Only]
I think you need to invest in a new mail setup.
> > Where does this affinity come from?
>
> The affinity comes from limiting the process to a certain subset of
> available cpus by modifying the cpus_ptr member of task_struck
> via taskset or numactl.
That's obviously not an answer. Why is that done?
next prev parent reply other threads:[~2022-02-09 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 15:59 [PATCH] sched/fair: Consider cpu affinity when allowing NUMA imbalance in find_idlest_group K Prateek Nayak
2022-02-08 10:51 ` Mel Gorman
2022-02-08 11:14 ` K Prateek Nayak
2022-02-09 10:46 ` Peter Zijlstra
2022-02-09 11:17 ` K Prateek Nayak
[not found] ` <MW2PR12MB237955DEA3F949359A96E031982E9@MW2PR12MB2379.namprd12.prod.outlook.com>
2022-02-09 17:20 ` Peter Zijlstra [this message]
2022-02-11 7:36 ` K Prateek Nayak
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=YgP30sLEQfYPsMZE@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=KPrateek.Nayak@amd.com \
--cc=aubrey.li@linux.intel.com \
--cc=efault@gmx.de \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=song.bao.hua@hisilicon.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.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