Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757305Ab3JKIkH (ORCPT ); Fri, 11 Oct 2013 04:40:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:65269 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753771Ab3JKIj7 (ORCPT ); Fri, 11 Oct 2013 04:39:59 -0400 Date: Fri, 11 Oct 2013 10:41:09 +0200 From: Alexander Gordeev To: Mark Lord Cc: "H. Peter Anvin" , Benjamin Herrenschmidt , linux-kernel@vger.kernel.org, Bjorn Helgaas , Ralf Baechle , Michael Ellerman , Martin Schwidefsky , Ingo Molnar , Tejun Heo , Dan Williams , Andy King , Jon Mason , Matt Porter , linux-pci@vger.kernel.org, linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org, linux390@de.ibm.com, linux-s390@vger.kernel.org, x86@kernel.org, linux-ide@vger.kernel.org, iss_storagedev@hp.com, linux-nvme@lists.infradead.org, linux-rdma@vger.kernel.org, netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net, linux-driver@qlogic.com, Solarflare linux maintainers , "VMware, Inc." , linux-scsi@vger.kernel.org Subject: Re: [PATCH RFC 00/77] Re-design MSI/MSI-X interrupts enablement pattern Message-ID: <20131011084108.GA25702@dhcp-26-207.brq.redhat.com> References: <5254D397.9030307@zytor.com> <1381292648.645.259.camel@pasglop> <20131010101704.GC11874@dhcp-26-207.brq.redhat.com> <5256D5AB.4050105@zytor.com> <20131010180704.GA15719@dhcp-26-207.brq.redhat.com> <5257357E.8080506@start.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5257357E.8080506@start.ca> 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: 3200 Lines: 113 On Thu, Oct 10, 2013 at 07:17:18PM -0400, Mark Lord wrote: > Just to help us all understand "the loop" issue.. > > Here's an example of driver code which uses the existing MSI-X interfaces, > for a device which can work with either 16, 8, 4, 2, or 1 MSI-X interrupt. > This is from a new driver I'm working on right now: > > > static int xx_alloc_msix_irqs (struct xx_dev *dev, int nvec) > { > xx_disable_all_irqs(dev); > do { > if (nvec < 2) > xx_prep_for_1_msix_vector(dev); > else if (nvec < 4) > xx_prep_for_2_msix_vectors(dev); > else if (nvec < 8) > xx_prep_for_4_msix_vectors(dev); > else if (nvec < 16) > xx_prep_for_8_msix_vectors(dev); > else > xx_prep_for_16_msix_vectors(dev); > nvec = pci_enable_msix(dev->pdev, dev->irqs, dev->num_vectors); > } while (nvec > 0); > > if (nvec) { > kerr(dev->name, "pci_enable_msix() failed, err=%d", nvec); > dev->num_vectors = 0; > return nvec; > } > return 0; /* success */ > } Yeah, that is a very good example. I would move all xx_prep_for__msix_vector() functions to a single helper i.e. xx_prep_msix_vectors(dev, ndev). Considering also (a) we do not want to waste unused platform resources associated with MSI-Xs and pull more quota than needed and (b) fixing couple of bugs, this function could look like this: static int xx_alloc_msix_irqs(struct xx_dev *dev, int nvec_in) { int nvec = roundup_pow_of_two(nvec_in); /* assume 0 > nvec_in <= 16 */ int rc; xx_disable_all_irqs(dev); retry: xx_prep_for_msix_vectors(dev, nvec); rc = pci_enable_msix(dev->pdev, dev->irqs, nvec); /* (b) */ if (rc > 0) { nvec = rounddown_pow_of_two(nvec); /* (a) */ goto retry; } if (rc) { kerr(dev->name, "pci_enable_msix() failed, err=%d", rc); dev->num_vectors = 0; return rc; } dev->num_vectors = nvec; /* (b) */ return 0; /* success */ } Now, this is a loop-free alternative: static int xx_alloc_msix_irqs(struct xx_dev *dev, int nvec) { nvec = roundup_pow_of_two(nvec); /* assume 0 > nvec <= 16 */ xx_disable_all_irqs(dev); pci_lock_msi(dev->pdev); rc = pci_get_msix_limit(dev->pdev, nvec); if (rc < 0) goto err; nvec = min(nvec, rc); /* if limit is more than requested */ nvec = rounddown_pow_of_two(nvec); /* (a) */ xx_prep_for_msix_vectors(dev, nvec); rc = pci_enable_msix(dev->pdev, dev->irqs, nvec); /* (b) */ if (rc < 0) goto err; pci_unlock_msi(dev->pdev); dev->num_vectors = nvec; /* (b) */ return 0; err: pci_unlock_msi(dev->pdev); kerr(dev->name, "pci_enable_msix() failed, err=%d", rc); dev->num_vectors = 0; return rc; } -- 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/