[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <262CB373A6D1F14F9B81E82F74F77D5A46F6F3A2@avmb2.qlogic.org>
Date: Sat, 22 Feb 2014 16:18:04 +0000
From: Shahed Shaikh <shahed.shaikh@...gic.com>
To: Alexander Gordeev <agordeev@...hat.com>,
Ben Hutchings <ben@...adent.org.uk>
CC: linux-kernel <linux-kernel@...r.kernel.org>,
Himanshu Madhani <himanshu.madhani@...gic.com>,
Rajesh Borundia <rajesh.borundia@...gic.com>,
Dept-Eng Linux Driver <Linux-Driver@...gic.com>,
netdev <netdev@...r.kernel.org>,
linux-pci <linux-pci@...r.kernel.org>
Subject: RE: [PATCH net-next 28/35] qlcnic: Use pci_enable_msix_range()
instead of pci_enable_msix()
> -----Original Message-----
> From: Alexander Gordeev [mailto:agordeev@...hat.com]
> Sent: Saturday, February 22, 2014 2:54 PM
> To: Ben Hutchings
> Cc: linux-kernel; Himanshu Madhani; Rajesh Borundia; Shahed Shaikh; Dept-
> Eng Linux Driver; netdev; linux-pci
> Subject: Re: [PATCH net-next 28/35] qlcnic: Use pci_enable_msix_range()
> instead of pci_enable_msix()
>
> On Sat, Feb 22, 2014 at 12:48:47AM +0000, Ben Hutchings wrote:
> > Sorry, I'm confused and this does work. But I wonder whether it is
> > really an improvement over using the old API.
>
> Slightly, as far as I am concerned - we just exchange tri-state oddity to re-
> enable MSI-X oddity. We're not going to improve drivers that can not work
> with any number of MSI-Xs from a range, like this one.
I will send a patch which will make use of available MSI-X number and remove the retry logic.
Thanks,
Shahed
--
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