From: "Michael S. Tsirkin" <mst@redhat.com>
To: Siwei Liu <loseweigh@gmail.com>
Cc: Jason Wang <jasowang@redhat.com>,
"Samudrala, Sridhar" <sridhar.samudrala@intel.com>,
virtualization@lists.linux-foundation.org,
virtio-dev@lists.oasis-open.org, "Brandeburg,
Jesse" <jesse.brandeburg@intel.com>,
Alexander Duyck <alexander.h.duyck@intel.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [virtio-dev] Re: [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
Date: Fri, 22 Jun 2018 05:30:43 +0300 [thread overview]
Message-ID: <20180622052717-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CADGSJ216itm89dUuK_vOfuBsBq5bq4485GqMKjB1JXFD_PLZxA@mail.gmail.com>
On Thu, Jun 21, 2018 at 06:07:18PM -0700, Siwei Liu wrote:
> On Thu, Jun 21, 2018 at 11:14 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > On Wed, Jun 13, 2018 at 01:40:59PM +0800, Jason Wang wrote:
> >>
> >>
> >> On 2018年06月13日 12:24, Samudrala, Sridhar wrote:
> >> > On 6/12/2018 7:38 PM, Jason Wang wrote:
> >> > >
> >> > >
> >> > > On 2018年06月12日 19:54, Michael S. Tsirkin wrote:
> >> > > > On Wed, Jun 06, 2018 at 10:29:03AM +0800, Jason Wang wrote:
> >> > > > >
> >> > > > > On 2018年06月05日 20:33, Michael S. Tsirkin wrote:
> >> > > > > > I don't think this is sufficient.
> >> > > > > >
> >> > > > > > If both primary and standby devices are present, a
> >> > > > > > legacy guest without
> >> > > > > > support for the feature might see two devices with same mac and get
> >> > > > > > confused.
> >> > > > > >
> >> > > > > > I think that we should only make primary visible after
> >> > > > > > guest acked the
> >> > > > > > backup feature bit.
> >> > > > > I think we want exactly the reverse? E.g fail the
> >> > > > > negotiation when guest
> >> > > > > does not ack backup feature.
> >> > > > >
> >> > > > > Otherwise legacy guest won't even have the chance to see
> >> > > > > primary device in
> >> > > > > the guest.
> >> > > > That's by design.
> >> > >
> >> > > So management needs to know the capability of guest to set the
> >> > > backup feature. This looks a chicken or egg problem to me.
> >> >
> >> > I don't think so. If the tenant requests 'accelerated datapath feature',
> >> > the management
> >> > will set 'standby' feature bit on virtio-net interface and if the guest
> >> > virtio-net driver
> >> > supports this feature, then the tenant VM will get that capability via a
> >> > hot-plugged
> >> > primary device.
> >>
> >> Ok, I thought exactly the reverse because of the commit title is "enable
> >> virtio_net to act as a standby for a passthru device". But re-read the
> >> commit log content, I understand the case a little bit. Btw, VF is not
> >> necessarily faster than virtio-net, especially consider virtio-net may have
> >> a lot of queues.
> >
> > Don't do that then, right?
>
> I don't understand. Where did the standby feature come to imply the
> "accelerated datapath" thing?
> Isn't failover/standby a generic high
> availblity term, rather than marry it to the concept of device model
> specifics? Do we expect scsi to work exactly the same way with
> "accelerated datapath"?
That's not what I said.
The semantics are that the primary is always used if present in
preference to standby.
Jason said virtio net is sometimes preferable.
If that's the case don't make it a standby.
More advanced use-cases do exist and e.g. Alexander Duyck
suggested using a switch-dev. failover isn't it though.
--
MST
next prev parent reply other threads:[~2018-06-22 2:30 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 23:09 [Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net Sridhar Samudrala
2018-06-05 1:41 ` Samudrala, Sridhar
2018-06-05 2:06 ` Jason Wang
2018-06-06 18:17 ` Samudrala, Sridhar
2018-06-06 18:52 ` [Qemu-devel] [libvirt] " Ján Tomko
2018-06-06 19:39 ` Samudrala, Sridhar
2018-06-06 18:53 ` [Qemu-devel] " Michael S. Tsirkin
2018-06-05 12:33 ` Michael S. Tsirkin
2018-06-05 20:20 ` Samudrala, Sridhar
2018-06-05 20:37 ` Michael S. Tsirkin
2018-06-05 21:16 ` [Qemu-devel] [virtio-dev] " Siwei Liu
2018-06-05 21:32 ` Michael S. Tsirkin
2018-06-05 22:09 ` Siwei Liu
2018-06-12 11:47 ` Michael S. Tsirkin
2018-06-14 0:56 ` Siwei Liu
2018-06-06 2:29 ` [Qemu-devel] " Jason Wang
2018-06-12 11:54 ` Michael S. Tsirkin
2018-06-13 0:20 ` Samudrala, Sridhar
2018-06-13 2:41 ` Jason Wang
2018-06-13 2:38 ` Jason Wang
2018-06-13 4:24 ` Samudrala, Sridhar
2018-06-13 5:40 ` Jason Wang
2018-06-21 18:14 ` Michael S. Tsirkin
2018-06-22 1:07 ` [Qemu-devel] [virtio-dev] " Siwei Liu
2018-06-22 2:30 ` Michael S. Tsirkin [this message]
2018-06-22 19:43 ` Siwei Liu
2018-06-22 21:47 ` Michael S. Tsirkin
2018-06-22 22:25 ` Siwei Liu
2018-06-22 22:28 ` Michael S. Tsirkin
2018-06-11 17:26 ` [Qemu-devel] " Michael S. Tsirkin
2018-06-12 1:54 ` Jason Wang
2018-06-12 2:17 ` Michael S. Tsirkin
2018-06-12 5:02 ` Samudrala, Sridhar
2018-06-12 11:34 ` Michael S. Tsirkin
2018-06-13 0:08 ` [Qemu-devel] [virtio-dev] " Samudrala, Sridhar
2018-06-14 1:02 ` Siwei Liu
2018-06-14 10:02 ` Cornelia Huck
2018-06-15 1:57 ` Siwei Liu
2018-06-15 11:48 ` Cornelia Huck
2018-06-15 17:06 ` Siwei Liu
2018-06-19 10:54 ` Cornelia Huck
2018-06-19 20:09 ` Siwei Liu
2018-06-20 14:34 ` Cornelia Huck
2018-06-20 19:59 ` Siwei Liu
2018-06-19 20:32 ` Michael S. Tsirkin
2018-06-20 9:53 ` Cornelia Huck
2018-06-20 14:11 ` Michael S. Tsirkin
2018-06-20 16:06 ` Cornelia Huck
2018-06-20 19:48 ` Michael S. Tsirkin
2018-06-21 14:59 ` Cornelia Huck
2018-06-21 18:20 ` Michael S. Tsirkin
2018-06-22 15:09 ` Cornelia Huck
2018-06-22 19:05 ` Michael S. Tsirkin
2018-06-22 20:21 ` Siwei Liu
2018-06-22 21:32 ` Michael S. Tsirkin
2018-06-22 21:57 ` Siwei Liu
2018-06-22 22:33 ` Michael S. Tsirkin
2018-06-23 0:05 ` Siwei Liu
2018-06-26 15:08 ` Cornelia Huck
2018-06-26 17:50 ` Michael S. Tsirkin
2018-06-27 9:11 ` Cornelia Huck
2018-06-25 9:55 ` Cornelia Huck
2018-06-26 1:46 ` Michael S. Tsirkin
2018-06-26 11:55 ` Cornelia Huck
2018-06-26 13:54 ` Michael S. Tsirkin
2018-06-22 21:43 ` Michael S. Tsirkin
2018-06-27 10:10 ` Cornelia Huck
2018-06-22 1:21 ` Siwei Liu
2018-06-22 2:25 ` Venu Busireddy
2018-06-22 2:32 ` Michael S. Tsirkin
2018-06-22 20:00 ` Siwei Liu
2018-06-22 20:03 ` Siwei Liu
2018-06-22 21:29 ` Michael S. Tsirkin
2018-06-22 21:51 ` Siwei Liu
2018-06-22 22:25 ` Michael S. Tsirkin
2018-06-22 23:40 ` Siwei Liu
2018-06-23 0:17 ` Siwei Liu
2018-06-24 1:45 ` Michael S. Tsirkin
2018-06-25 17:54 ` Samudrala, Sridhar
2018-06-26 1:50 ` Michael S. Tsirkin
2018-06-26 15:17 ` Cornelia Huck
2018-06-26 15:38 ` Michael S. Tsirkin
2018-06-26 16:03 ` Cornelia Huck
2018-06-26 17:42 ` Michael S. Tsirkin
2018-06-26 23:38 ` Siwei Liu
2018-06-27 0:29 ` Michael S. Tsirkin
2018-06-27 6:21 ` Siwei Liu
2018-06-27 6:49 ` Samudrala, Sridhar
2018-06-27 7:03 ` Siwei Liu
2018-06-15 2:34 ` Michael S. Tsirkin
2018-06-15 9:32 ` Cornelia Huck
2018-06-15 12:31 ` Michael S. Tsirkin
2018-06-18 13:27 ` Cornelia Huck
2018-06-14 12:50 ` 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=20180622052717-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=jasowang@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=loseweigh@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sridhar.samudrala@intel.com \
--cc=virtio-dev@lists.oasis-open.org \
--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).