[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131024110135.GD13159@mtj.dyndns.org>
Date: Thu, 24 Oct 2013 12:01:35 +0100
From: Tejun Heo <tj@...nel.org>
To: David Laight <David.Laight@...LAB.COM>
Cc: Alexander Gordeev <agordeev@...hat.com>,
linux-kernel@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>,
Michael Ellerman <michael@...erman.id.au>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Ben Hutchings <bhutchings@...arflare.com>,
Mark Lord <kernel@...rt.ca>, "H. Peter Anvin" <hpa@...or.com>,
linux-pci@...r.kernel.org
Subject: Re: [PATCH RFC v2 12/29] PCI/MSI: Introduce pcim_enable_msi*()
family helpers
Hello,
On Thu, Oct 24, 2013 at 11:57:40AM +0100, David Laight wrote:
> > > ...would turn into a single helper call....
> > >
> > > rc = pcim_enable_msix_range(adapter->pdev,
> > > adapter->msix_entries,
> > > nvec,
> > > FOO_DRIVER_MINIMUM_NVEC);
> >
> > I haven't looked into any details but, if the above works for most use
> > cases, it looks really good to me.
>
> The one case it doesn't work is where the driver either
> wants the full number or the minimum number - but not
> a value in between.
>
> Might be worth adding an extra parameter so that this
> (and maybe other) odd requirements can be met.
>
> Some static inline functions could be used for the common cases.
If those are edge cases, I don't think it's a big deal no matter what
we do.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists