On Tue, Jun 10, 2014 at 01:47:09PM -0700, Stephen Hemminger wrote:
> On Tue, 10 Jun 2014 19:26:08 +
> "Carew, Alan" wrote:
>
> > One alternative for us is then to take Neil Horman's idea of scanning
> > /sys/bus/pci/devices//msi_irqs/
> > This gives us at least (MSI | MSI-X) | INT-X, however
-Original Message-
From: Stephen Hemminger [mailto:step...@networkplumber.org]
Sent: Tuesday, June 10, 2014 6:41 PM
To: Carew, Alan
Cc: dev at dpkd.org
Subject: Re: [PATCH 00/10] igb_uio patches
On Tue, 10 Jun 2014 15:33:31 +
"Carew, Alan" wrote:
> Good catches and fixes in this set
> These apply to the current DPDK tree, and are an alternative to the patches
> from Alan. It provides indication of IRQ mode via sysfs attribute. They
> include
> cleanups and fixes to allow use of MSI and do proper fallback for the case
> where MSI-X vectors are exhausted.
>
> Hi Stephen,
>
>
-Original Message-
From: Stephen Hemminger [mailto:step...@networkplumber.org]
Sent: Friday, June 06, 2014 10:27 PM
To: Carew, Alan
Cc: dev at dpkd.org
Subject: [PATCH 00/10] igb_uio patches
These apply to the current DPDK tree, and are an alternative to
the patches from Alan. It provide
On Tue, 10 Jun 2014 19:26:08 +
"Carew, Alan" wrote:
> A question then, how does uio_pci_generic handle interrupt modes in terms of
> userspace interface when determining the configured interrupt mode?
uio_pci_generic only handles INTX disable, and nothing else. It doesn't do MSI
or allow IR
On Tue, 10 Jun 2014 19:26:08 +
"Carew, Alan" wrote:
> One alternative for us is then to take Neil Horman's idea of scanning
> /sys/bus/pci/devices//msi_irqs/
> This gives us at least (MSI | MSI-X) | INT-X, however the Virtio
> specification mentions MSI-X explicitly for determining the corr
6 matches
Mail list logo
