Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753138AbbGOO4g (ORCPT ); Wed, 15 Jul 2015 10:56:36 -0400 Received: from foss.arm.com ([217.140.101.70]:39540 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751502AbbGOO4e (ORCPT ); Wed, 15 Jul 2015 10:56:34 -0400 Message-ID: <55A6749E.7040803@arm.com> Date: Wed, 15 Jul 2015 15:56:30 +0100 From: Marc Zyngier Organization: ARM Ltd User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: Christoph Hellwig , "ksummit-discuss@lists.linuxfoundation.org" CC: "linux-rdma@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-nvme@lists.infradead.org" Subject: Re: [Ksummit-discuss] [TECH TOPIC] IRQ affinity References: <20150715120708.GA24534@infradead.org> In-Reply-To: <20150715120708.GA24534@infradead.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1592 Lines: 37 On 15/07/15 13:07, Christoph Hellwig wrote: > Many years ago we decided to move setting of IRQ to core affnities to > userspace with the irqbalance daemon. > > These days we have systems with lots of MSI-X vector, and we have > hardware and subsystem support for per-CPU I/O queues in the block > layer, the RDMA subsystem and probably the network stack (I'm not too > familar with the recent developments there). It would really help the > out of the box performance and experience if we could allow such > subsystems to bind interrupt vectors to the node that the queue is > configured on. > > I'd like to discuss if the rationale for moving the IRQ affinity setting > fully to userspace are still correct in todays world any any pitfalls > we'll have to learn from in irqbalanced and the old in-kernel affinity > code. I've been pondering about having some notion of "grouping", where some interrupts are logically part of the same working set, and it doesn't make much sense to spread it among CPUs, and userspace doesn't really have a clue about this. A related problem is that some weird HW (things like cascaded interrupt controllers) can only move a bunch of interrupt in one go, which isn't really what userspace expects to see (move one interrupt, see another 31 moving). Thanks, M. -- Jazz is not dead. It just smells funny... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/