From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Dreier Subject: Re: [PATCH] mlx4_core: request MSIX vectors as much as there CPU cores Date: Wed, 05 May 2010 12:55:54 -0700 Message-ID: References: <20100505113047.GA12242@mtldesk030.lab.mtl.com> <20100505163252.GG15969@obsidianresearch.com> <4BE1C82F.4000009@mellanox.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: (Roland Dreier's message of "Wed, 05 May 2010 12:51:19 -0700") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ewg-bounces-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org Errors-To: ewg-bounces-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org To: tziporet-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org Cc: Jason Gunthorpe , Linux RDMA list , ewg , Eli Cohen List-Id: linux-rdma@vger.kernel.org > We found it in performance work of our EN (10G) driver By the way, it would certainly make sense for the ethernet driver to use a number of queues that matches num_online_cpus() at the time the interface is brought up. Since we can't change the # of MSI-X vectors very easily I think we need to allow for the possible CPUs, but bouncing a net interface seems lighter weight to me. Although perhaps reloading a driver on CPU hotplug is OK too? - R. -- Roland Dreier || For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html