From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Christoph Hellwig <hch@infradead.org>,
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 20:49:48 +0200 [thread overview]
Message-ID: <20170227204931-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170227204456-mutt-send-email-mst@kernel.org>
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 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.
>
> Sorry I've been a bit busy. Any chance you could rebase?
> This conflicts with your patch removing vq info.
Actually it doesn't, my bad. Applied now, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Christoph Hellwig <hch@infradead.org>,
pbonzini@redhat.com
Subject: Re: automatic IRQ affinity for virtio V3
Date: Mon, 27 Feb 2017 20:49:48 +0200 [thread overview]
Message-ID: <20170227204931-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170227204456-mutt-send-email-mst@kernel.org>
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 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.
>
> Sorry I've been a bit busy. Any chance you could rebase?
> This conflicts with your patch removing vq info.
Actually it doesn't, my bad. Applied now, thanks!
next prev parent reply other threads:[~2017-02-27 18:49 UTC|newest]
Thread overview: 38+ 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-05 17:15 ` Christoph Hellwig
2017-02-07 7:17 ` Jason Wang
2017-02-07 7:17 ` Jason Wang
2017-02-07 9:38 ` Christoph Hellwig
2017-02-07 9:38 ` Christoph Hellwig
2017-02-08 2:52 ` Jason Wang
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-05 17:15 ` Christoph Hellwig
2017-02-07 7:17 ` Jason Wang
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 ` Christoph Hellwig
2017-02-05 17:15 ` [PATCH 4/9] virtio_pci: simplify MSI-X setup Christoph Hellwig
2017-02-05 17:15 ` 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 ` 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 ` 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 ` Christoph Hellwig
2017-02-05 17:15 ` [PATCH 8/9] virtio_blk: use virtio IRQ affinity Christoph Hellwig
2017-02-05 17:15 ` Christoph Hellwig
2017-02-05 17:15 ` [PATCH 9/9] virtio_scsi: " Christoph Hellwig
2017-02-05 17:15 ` Christoph Hellwig
2017-02-09 13:50 ` automatic IRQ affinity for virtio V3 Christoph Hellwig
2017-02-09 13:50 ` Christoph Hellwig
2017-02-09 16:01 ` Michael S. Tsirkin
2017-02-09 16:01 ` Michael S. Tsirkin
2017-02-27 8:48 ` Christoph Hellwig
2017-02-27 8:48 ` Christoph Hellwig
2017-02-27 18:45 ` Michael S. Tsirkin
2017-02-27 18:45 ` Michael S. Tsirkin
2017-02-27 18:49 ` Michael S. Tsirkin [this message]
2017-02-27 18:49 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2017-02-05 17:15 Christoph Hellwig
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=20170227204931-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.