Re: automatic IRQ affinity for virtio V3

2017-02-27 Thread Michael S. Tsirkin
On Mon, Feb 27, 2017 at 09:48:32AM +0100, Christoph Hellwig wrote: > On Thu, Feb 09, 2017 at 06:01:57PM +0200, Michael S. Tsirkin wrote: > > > Any chance to get this in for 4.11 after I got reviews from Jason > > > for most of the patches? > > > > Absolutely, I intend to merge it. > > So, what

Re: automatic IRQ affinity for virtio V3

2017-02-27 Thread Michael S. Tsirkin
On Mon, Feb 27, 2017 at 09:48:32AM +0100, Christoph Hellwig wrote: > On Thu, Feb 09, 2017 at 06:01:57PM +0200, Michael S. Tsirkin wrote: > > > Any chance to get this in for 4.11 after I got reviews from Jason > > > for most of the patches? > > > > Absolutely, I intend to merge it. > > So, what

Re: automatic IRQ affinity for virtio V3

2017-02-27 Thread Michael S. Tsirkin
On Mon, Feb 27, 2017 at 08:45:25PM +0200, Michael S. Tsirkin wrote: > On Mon, Feb 27, 2017 at 09:48:32AM +0100, Christoph Hellwig wrote: > > On Thu, Feb 09, 2017 at 06:01:57PM +0200, Michael S. Tsirkin wrote: > > > > Any chance to get this in for 4.11 after I got reviews from Jason > > > > for

Re: automatic IRQ affinity for virtio V3

2017-02-27 Thread Michael S. Tsirkin
On Mon, Feb 27, 2017 at 08:45:25PM +0200, Michael S. Tsirkin wrote: > On Mon, Feb 27, 2017 at 09:48:32AM +0100, Christoph Hellwig wrote: > > On Thu, Feb 09, 2017 at 06:01:57PM +0200, Michael S. Tsirkin wrote: > > > > Any chance to get this in for 4.11 after I got reviews from Jason > > > > for

Re: automatic IRQ affinity for virtio V3

2017-02-27 Thread Christoph Hellwig
On Thu, Feb 09, 2017 at 06:01:57PM +0200, Michael S. Tsirkin wrote: > > Any chance to get this in for 4.11 after I got reviews from Jason > > for most of the patches? > > Absolutely, I intend to merge it. So, what is the plan for virtio this merge window? No changes seem to have made it into

Re: automatic IRQ affinity for virtio V3

2017-02-27 Thread Christoph Hellwig
On Thu, Feb 09, 2017 at 06:01:57PM +0200, Michael S. Tsirkin wrote: > > Any chance to get this in for 4.11 after I got reviews from Jason > > for most of the patches? > > Absolutely, I intend to merge it. So, what is the plan for virtio this merge window? No changes seem to have made it into

Re: automatic IRQ affinity for virtio V3

2017-02-09 Thread Michael S. Tsirkin
On Thu, Feb 09, 2017 at 05:50:31AM -0800, Christoph Hellwig wrote: > On Sun, Feb 05, 2017 at 06:15:17PM +0100, Christoph Hellwig wrote: > > Hi Michael, hi Jason, > > > > This patches applies a few cleanups to the virtio PCI interrupt handling > > code, and then converts the virtio PCI code to use

Re: automatic IRQ affinity for virtio V3

2017-02-09 Thread Michael S. Tsirkin
On Thu, Feb 09, 2017 at 05:50:31AM -0800, Christoph Hellwig wrote: > On Sun, Feb 05, 2017 at 06:15:17PM +0100, Christoph Hellwig wrote: > > Hi Michael, hi Jason, > > > > This patches applies a few cleanups to the virtio PCI interrupt handling > > code, and then converts the virtio PCI code to use

Re: automatic IRQ affinity for virtio V3

2017-02-09 Thread Christoph Hellwig
On Sun, Feb 05, 2017 at 06:15:17PM +0100, Christoph Hellwig wrote: > Hi Michael, hi Jason, > > This patches applies a few cleanups to the virtio PCI interrupt handling > code, and then converts the virtio PCI code to use the automatic MSI-X > vectors spreading, as well as using the information in

Re: automatic IRQ affinity for virtio V3

2017-02-09 Thread Christoph Hellwig
On Sun, Feb 05, 2017 at 06:15:17PM +0100, Christoph Hellwig wrote: > Hi Michael, hi Jason, > > This patches applies a few cleanups to the virtio PCI interrupt handling > code, and then converts the virtio PCI code to use the automatic MSI-X > vectors spreading, as well as using the information in

automatic IRQ affinity for virtio V3

2017-02-05 Thread Christoph Hellwig
Hi Michael, hi Jason, This patches applies a few cleanups to the virtio PCI interrupt handling code, and then converts the virtio PCI code to use the automatic MSI-X vectors spreading, as well as using the information in virtio-blk and virtio-scsi to automatically align the blk-mq queues to the

automatic IRQ affinity for virtio V3

2017-02-05 Thread Christoph Hellwig
Hi Michael, hi Jason, This patches applies a few cleanups to the virtio PCI interrupt handling code, and then converts the virtio PCI code to use the automatic MSI-X vectors spreading, as well as using the information in virtio-blk and virtio-scsi to automatically align the blk-mq queues to the

automatic IRQ affinity for virtio V2

2017-01-27 Thread Christoph Hellwig
Hi Michael, hi Jason, This patches applies a few cleanups to the virtio PCI interrupt handling code, and then converts the virtio PCI code to use the automatic MSI-X vectors spreading, as well as using the information in virtio-blk and virtio-scsi to automatically align the blk-mq queues to the

automatic IRQ affinity for virtio V2

2017-01-27 Thread Christoph Hellwig
Hi Michael, hi Jason, This patches applies a few cleanups to the virtio PCI interrupt handling code, and then converts the virtio PCI code to use the automatic MSI-X vectors spreading, as well as using the information in virtio-blk and virtio-scsi to automatically align the blk-mq queues to the

Re: automatic IRQ affinity for virtio

2016-12-07 Thread Christoph Hellwig
On Sun, Nov 27, 2016 at 05:37:04AM +0200, Michael S. Tsirkin wrote: > On Fri, Nov 25, 2016 at 08:25:38AM +0100, Christoph Hellwig wrote: > > Btw, what's the best way to get any response to this series? > > But this and the predecessor seem to have completly fallen on deaf > > ears. > > I'm sorry,

Re: automatic IRQ affinity for virtio

2016-12-07 Thread Christoph Hellwig
On Sun, Nov 27, 2016 at 05:37:04AM +0200, Michael S. Tsirkin wrote: > On Fri, Nov 25, 2016 at 08:25:38AM +0100, Christoph Hellwig wrote: > > Btw, what's the best way to get any response to this series? > > But this and the predecessor seem to have completly fallen on deaf > > ears. > > I'm sorry,

Re: automatic IRQ affinity for virtio

2016-11-26 Thread Michael S. Tsirkin
On Fri, Nov 25, 2016 at 08:25:38AM +0100, Christoph Hellwig wrote: > Btw, what's the best way to get any response to this series? > But this and the predecessor seem to have completly fallen on deaf > ears. I'm sorry, I intend to review soon and if OK merge it. The fact that it depends on tip

Re: automatic IRQ affinity for virtio

2016-11-26 Thread Michael S. Tsirkin
On Fri, Nov 25, 2016 at 08:25:38AM +0100, Christoph Hellwig wrote: > Btw, what's the best way to get any response to this series? > But this and the predecessor seem to have completly fallen on deaf > ears. I'm sorry, I intend to review soon and if OK merge it. The fact that it depends on tip

Re: automatic IRQ affinity for virtio

2016-11-24 Thread Christoph Hellwig
Btw, what's the best way to get any response to this series? But this and the predecessor seem to have completly fallen on deaf ears.

Re: automatic IRQ affinity for virtio

2016-11-24 Thread Christoph Hellwig
Btw, what's the best way to get any response to this series? But this and the predecessor seem to have completly fallen on deaf ears.

automatic IRQ affinity for virtio

2016-11-17 Thread Christoph Hellwig
Hi Michael, this series contains a couple cleanups for the virtio_pci interrupt handling code, including a switch to the new pci_irq_alloc_vectors helper, and support for automatic affinity by the PCI layer if the consumers ask for it. It then converts over virtio_blk to use this functionality

automatic IRQ affinity for virtio

2016-11-17 Thread Christoph Hellwig
Hi Michael, this series contains a couple cleanups for the virtio_pci interrupt handling code, including a switch to the new pci_irq_alloc_vectors helper, and support for automatic affinity by the PCI layer if the consumers ask for it. It then converts over virtio_blk to use this functionality