Re: [PATCH RFC 34/77] ioat: Update MSI/MSI-X interrupts enablement code

2013-10-03 Thread Dan Williams
On Thu, Oct 3, 2013 at 1:12 PM, Alexander Gordeev wrote: > On Wed, Oct 02, 2013 at 11:00:51AM -0700, Williams, Dan J wrote: >> I see patch 00/77 now and I still don't see the need for ioatdma to be >> updated. If we fail the subsequent request_irq, the driver will still >> fall back to trying

Re: [PATCH RFC 34/77] ioat: Update MSI/MSI-X interrupts enablement code

2013-10-03 Thread Alexander Gordeev
On Wed, Oct 02, 2013 at 11:00:51AM -0700, Williams, Dan J wrote: > I see patch 00/77 now and I still don't see the need for ioatdma to be > updated. If we fail the subsequent request_irq, the driver will still > fall back to trying less interrupts. In the proposed design pci_enable_msix() will

Re: [PATCH RFC 34/77] ioat: Update MSI/MSI-X interrupts enablement code

2013-10-03 Thread Alexander Gordeev
On Wed, Oct 02, 2013 at 11:00:51AM -0700, Williams, Dan J wrote: I see patch 00/77 now and I still don't see the need for ioatdma to be updated. If we fail the subsequent request_irq, the driver will still fall back to trying less interrupts. In the proposed design pci_enable_msix() will

Re: [PATCH RFC 34/77] ioat: Update MSI/MSI-X interrupts enablement code

2013-10-03 Thread Dan Williams
On Thu, Oct 3, 2013 at 1:12 PM, Alexander Gordeev agord...@redhat.com wrote: On Wed, Oct 02, 2013 at 11:00:51AM -0700, Williams, Dan J wrote: I see patch 00/77 now and I still don't see the need for ioatdma to be updated. If we fail the subsequent request_irq, the driver will still fall back

[PATCH RFC 34/77] ioat: Update MSI/MSI-X interrupts enablement code

2013-10-02 Thread Alexander Gordeev
As result of recent re-design of the MSI/MSI-X interrupts enabling pattern this driver has to be updated to use the new technique to obtain a optimal number of MSI/MSI-X interrupts required. Signed-off-by: Alexander Gordeev --- drivers/dma/ioat/dma.c | 10 +++--- 1 files changed, 7

Re: [PATCH RFC 34/77] ioat: Update MSI/MSI-X interrupts enablement code

2013-10-02 Thread Williams, Dan J
On Wed, Oct 2, 2013 at 10:31 AM, Williams, Dan J wrote: > [ dropping all cc's except lkml ] > > On Wed, Oct 2, 2013 at 3:48 AM, Alexander Gordeev wrote: >> As result of recent re-design of the MSI/MSI-X interrupts enabling >> pattern this driver has to be updated to use the new technique to >>

Re: [PATCH RFC 34/77] ioat: Update MSI/MSI-X interrupts enablement code

2013-10-02 Thread Williams, Dan J
[ dropping all cc's except lkml ] On Wed, Oct 2, 2013 at 3:48 AM, Alexander Gordeev wrote: > As result of recent re-design of the MSI/MSI-X interrupts enabling > pattern this driver has to be updated to use the new technique to > obtain a optimal number of MSI/MSI-X interrupts required. > What

Re: [PATCH RFC 34/77] ioat: Update MSI/MSI-X interrupts enablement code

2013-10-02 Thread Williams, Dan J
[ dropping all cc's except lkml ] On Wed, Oct 2, 2013 at 3:48 AM, Alexander Gordeev agord...@redhat.com wrote: As result of recent re-design of the MSI/MSI-X interrupts enabling pattern this driver has to be updated to use the new technique to obtain a optimal number of MSI/MSI-X interrupts

Re: [PATCH RFC 34/77] ioat: Update MSI/MSI-X interrupts enablement code

2013-10-02 Thread Williams, Dan J
On Wed, Oct 2, 2013 at 10:31 AM, Williams, Dan J dan.j.willi...@intel.com wrote: [ dropping all cc's except lkml ] On Wed, Oct 2, 2013 at 3:48 AM, Alexander Gordeev agord...@redhat.com wrote: As result of recent re-design of the MSI/MSI-X interrupts enabling pattern this driver has to be

[PATCH RFC 34/77] ioat: Update MSI/MSI-X interrupts enablement code

2013-10-02 Thread Alexander Gordeev
As result of recent re-design of the MSI/MSI-X interrupts enabling pattern this driver has to be updated to use the new technique to obtain a optimal number of MSI/MSI-X interrupts required. Signed-off-by: Alexander Gordeev agord...@redhat.com --- drivers/dma/ioat/dma.c | 10 +++--- 1