From: Christoph Hellwig <hch@lst.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Christoph Hellwig <hch@lst.de>,
jasowang@redhat.com, axboe@kernel.dk, pbonzini@redhat.com,
virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: automatic IRQ affinity for virtio V3
Date: Mon, 27 Feb 2017 09:48:32 +0100 [thread overview]
Message-ID: <20170227084832.GA22373@lst.de> (raw)
In-Reply-To: <20170209180130-mutt-send-email-mst@kernel.org>
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 linux-next before the merge window, never mind
a week into it.
next prev parent reply other threads:[~2017-02-27 8:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 17:15 automatic IRQ affinity for virtio V3 Christoph Hellwig
2017-02-05 17:15 ` [PATCH 1/9] virtio_pci: remove struct virtio_pci_vq_info Christoph Hellwig
2017-02-07 7:17 ` Jason Wang
2017-02-07 9:38 ` Christoph Hellwig
2017-02-08 2:52 ` Jason Wang
2017-02-05 17:15 ` [PATCH 2/9] virtio_pci: use shared interrupts for virtqueues Christoph Hellwig
2017-02-07 7:17 ` Jason Wang
2017-02-05 17:15 ` [PATCH 3/9] virtio_pci: don't duplicate the msix_enable flag in struct pci_dev Christoph Hellwig
2017-02-05 17:15 ` [PATCH 4/9] virtio_pci: simplify MSI-X setup Christoph Hellwig
2017-02-05 17:15 ` [PATCH 5/9] virtio: allow drivers to request IRQ affinity when creating VQs Christoph Hellwig
2017-02-05 17:15 ` [PATCH 6/9] virtio: provide a method to get the IRQ affinity mask for a virtqueue Christoph Hellwig
2017-02-05 17:15 ` [PATCH 7/9] blk-mq: provide a default queue mapping for virtio device Christoph Hellwig
2017-02-05 17:15 ` [PATCH 8/9] virtio_blk: use virtio IRQ affinity Christoph Hellwig
2017-02-05 17:15 ` [PATCH 9/9] virtio_scsi: " Christoph Hellwig
2017-02-09 13:50 ` automatic IRQ affinity for virtio V3 Christoph Hellwig
2017-02-09 16:01 ` Michael S. Tsirkin
2017-02-27 8:48 ` Christoph Hellwig [this message]
2017-02-27 18:45 ` Michael S. Tsirkin
2017-02-27 18:49 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170227084832.GA22373@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).