[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR0501MB2429A6F8FDBD6DC9E835BE66C47D0@VI1PR0501MB2429.eurprd05.prod.outlook.com>
Date: Mon, 16 Jan 2017 22:21:54 +0000
From: Daniel Jurgens <danielj@...lanox.com>
To: Or Gerlitz <gerlitz.or@...il.com>
CC: Tariq Toukan <tariqt@...lanox.com>,
"David S. Miller" <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
"Eran Ben Elisha" <eranbe@...lanox.com>
Subject: Re: [PATCH net-next 3/9] net/mlx4_core: Set EQ affinity hint to local
NUMA CPUs
On 1/16/2017 3:59 PM, Or Gerlitz wrote:
> On Mon, Jan 16, 2017 at 11:54 PM, Daniel Jurgens <danielj@...lanox.com> wrote:
>> On 1/16/2017 3:44 PM, Or Gerlitz wrote:
>>> On Mon, Jan 16, 2017 at 7:29 PM, Tariq Toukan <tariqt@...lanox.com> wrote:
>>>> From: Daniel Jurgens <danielj@...lanox.com>
>>>>
>>>> Use CPUs on the close NUMA when setting the EQ affinity hints.
>>> Dan, are we sure there are no down-sides for always doing this? this
>>> code is probably there for many years and we're introducing here new
>>> behaviour to potentially to many Ms installs when they get distro
>>> update that includes this patch.
>
>> I don't see a downside, this just favors using the node local CPUs before others.
> OK, so this just favors before others and not limits (not in front of
> the code now)? would be good to improve the change log and make this
> clear.
Right, doesn't limit. Just favors the local node. I can work with Tariq to update the commit message if you think it necessary.
Powered by blists - more mailing lists