Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752781Ab3JYJ7P (ORCPT ); Fri, 25 Oct 2013 05:59:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47376 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752099Ab3JYJ7O (ORCPT ); Fri, 25 Oct 2013 05:59:14 -0400 Date: Fri, 25 Oct 2013 12:01:04 +0200 From: Alexander Gordeev To: David Laight Cc: Mark Lord , Tejun Heo , linux-kernel@vger.kernel.org, Bjorn Helgaas , Michael Ellerman , Benjamin Herrenschmidt , Ben Hutchings , "H. Peter Anvin" , linux-pci@vger.kernel.org Subject: Re: [PATCH RFC v2 12/29] PCI/MSI: Introduce pcim_enable_msi*() family helpers Message-ID: <20131025100103.GA317@dhcp-26-207.brq.redhat.com> References: <6bc575621ef70f72b206e4aa944acd32f1a75718.1382103786.git.agordeev@redhat.com> <20131024105158.GB13159@mtj.dyndns.org> <20131024114133.GA26610@dhcp-26-207.brq.redhat.com> <5269D5D1.60103@start.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 896 Lines: 26 On Fri, Oct 25, 2013 at 10:10:02AM +0100, David Laight wrote: > What this doesn't resolve is a driver requesting a lot of interrupts > early on and leaving none for later drivers. If this problem really exists anywhere besides pSeries? I can imagine x86 hitting lack of vectors in interrupt table when number of CPUs exceeds hundreds, but do we have this problem now? > Really the system needs to allocate the minimum number to all > drivers before giving out any extra ones - I've NFI how this > would be arranged! Do not know. The pSeries quota approach seems more reasonable to me. > David -- Regards, Alexander Gordeev agordeev@redhat.com -- 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/