From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: mlx5 broken affinity Date: Thu, 2 Nov 2017 13:13:30 +0100 Message-ID: <20171102121330.GD4772@lunn.ch> References: <2187e555-2c4e-ef55-1c3a-17f5af54d762@fb.com> <573060a9-19a7-9133-ef52-fa947088dabb@fb.com> <3af0c164-8dde-b6f0-45e1-edbbb28e7f73@mellanox.com> <83d3944f-8a31-eb31-93db-294906630b0e@grimberg.me> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Tariq Toukan , Jes Sorensen , Saeed Mahameed , Networking , Leon Romanovsky , Saeed Mahameed , Kernel Team , Christoph Hellwig , Thomas Gleixner To: Sagi Grimberg Return-path: Received: from vps0.lunn.ch ([185.16.172.187]:38836 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752139AbdKBMNe (ORCPT ); Thu, 2 Nov 2017 08:13:34 -0400 Content-Disposition: inline In-Reply-To: <83d3944f-8a31-eb31-93db-294906630b0e@grimberg.me> Sender: netdev-owner@vger.kernel.org List-ID: > >This means that if your NIC is on NUMA #1, and you reduce the number of > >channels, you might end up working only with the cores on the far NUMA. > >Not good! > We deliberated on this before, and concluded that application affinity > and device affinity are equally important. If you have a real use case > that shows otherwise, its perfectly doable to start from the device home > node. Hi Sagi You might find this talk at NetDev interesting: https://www.netdevconf.org/2.2/session.html?shochat-devicemgmt-talk Andrew