Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932167Ab3IZLgc (ORCPT ); Thu, 26 Sep 2013 07:36:32 -0400 Received: from mx0.aculab.com ([213.249.233.131]:45881 "HELO mx0.aculab.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S932145Ab3IZLga convert rfc822-to-8bit (ORCPT ); Thu, 26 Sep 2013 07:36:30 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8BIT Subject: RE: [PATCH v2 2/6] PCI/MSI: Factor out pci_get_msi_cap() interface Date: Thu, 26 Sep 2013 12:34:36 +0100 Message-ID: In-Reply-To: <20130926104548.GB16774@dhcp-26-207.brq.redhat.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PATCH v2 2/6] PCI/MSI: Factor out pci_get_msi_cap() interface Thread-Index: Ac66pQvfp+gO4C/oRkGe0omuPs+SxAABpdcg References: <20130918094759.GA2353@dhcp-26-207.brq.redhat.com> <20130918142231.GA21650@mtj.dyndns.org> <20130918165045.GB2353@dhcp-26-207.brq.redhat.com> <20130920082458.GA10507@dhcp-26-207.brq.redhat.com> <20130920122736.GD7630@mtj.dyndns.org> <20130925180220.GB26273@google.com> <20130925205804.GA21737@dhcp-26-207.brq.redhat.com> <20130925210016.GA8926@htj.dyndns.org> <20130926074646.GA16774@dhcp-26-207.brq.redhat.com> <20130926104548.GB16774@dhcp-26-207.brq.redhat.com> From: "David Laight" To: "Alexander Gordeev" Cc: "Tejun Heo" , , "Joerg Roedel" , , , , "Jan Beulich" , "Bjorn Helgaas" , , "Ingo Molnar" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 987 Lines: 25 > On Thu, Sep 26, 2013 at 09:58:53AM +0100, David Laight wrote: > > Would it be possible to do some kind of 2-stage allocation. > > In the first pass the driver would pass a minimum and desired > > number of MSI-X interrupts, but not actually be given any. > > Repeated calls to msi_enable_msi/msix() is what we are trying to avoid. I was thinking that the first call would be done during driver probe (assuming such a time exists) so that the subsystem could determine how many interrupts all the drivers would like, so it can then hand out a smaller number to some of the early drivers in order to have some left to satisfy the minimum requirement of later ones. So all it would do is sum the requirements of all the drivers. David -- 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/