From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Sridhar Samudrala <sridhar.samudrala@intel.com>,
virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] [PATCH] content: Introduce VIRTIO_NET_F_STANDBY feature
Date: Mon, 23 Jul 2018 11:03:11 +0200 [thread overview]
Message-ID: <20180723110311.5a36f56a.cohuck@redhat.com> (raw)
In-Reply-To: <20180722182834-mutt-send-email-mst@kernel.org>
On Sun, 22 Jul 2018 18:37:42 +0300
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Fri, Jul 20, 2018 at 09:44:50AM +0200, Cornelia Huck wrote:
> > On Thu, 19 Jul 2018 14:29:40 -0700
> > Sridhar Samudrala <sridhar.samudrala@intel.com> wrote:
> >
> > > VIRTIO_NET_F_STANDBY feature enables hypervisor to indicate virtio_net
> > > driver to act as a standby for another device with the same MAC address.
> > >
> > > Signed-off-by: Sridhar Samudrala <sridhar.samudrala@intel.com
> > > ---
> > > content.tex | 10 ++++++++++
> > > 1 file changed, 10 insertions(+)
> > > @@ -2636,6 +2639,13 @@ If the driver negotiates VIRTIO_NET_F_MTU, it MUST NOT transmit packets of
> > > size exceeding the value of \field{mtu} (plus low level ethernet header length)
> > > with \field{gso_type} NONE or ECN.
> > >
> > > +A driver SHOULD negotiate VIRTIO_NET_F_STANDBY feature if the device offers it.
> >
> > I'm not sure that this is the right section of the spec. Maybe we need
> > a new normative driver section for "cross-device features" (better
> > names wanted :), and the same for devices?
>
> You mean if we ever extend this to non-network devices?
> This is a network specific feature bit so what makes
> it a cross-device feature?
No, the network device location is alright. But it is in a section that
deals with how the config space etc. is handled, and I'm not sure
whether it fits well with the other statements in there. Not a major
gripe, though.
>
> > > +
> > > +If the driver negotiates VIRTIO_NET_F_STANDBY, it should act as a standby
> > for
> > > +another device with the same MAC address when available. The hypervisor can
> > > +hot-plug a primary device with same MAC address if the feature is successfully
> > > +negotiated with the driver.
> >
> > I don't think you should add implementation details like hotplugging
> > into the spec.
> >
> > What about:
> >
> > "If the driver negotiates VIRTIO_NET_F_STANDBY, the device MAY act as a
> > standby device for another device with the same MAC address, the
> > 'failover device'.
>
> I find the name "failover device" confusing. Linux came up with
> names primary and standby.
"...the device MAY act as a standby device for a primary device with
the same MAC address."
?
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2018-07-23 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 21:29 [virtio-dev] [PATCH] content: Introduce VIRTIO_NET_F_STANDBY feature Sridhar Samudrala
2018-07-20 7:44 ` Cornelia Huck
2018-07-22 15:37 ` Michael S. Tsirkin
2018-07-23 9:03 ` Cornelia Huck [this message]
2018-07-23 9:22 ` Michael S. Tsirkin
2018-07-23 9:30 ` Cornelia Huck
2018-07-20 8:41 ` Siwei Liu
2018-07-20 9:14 ` Cornelia Huck
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=20180723110311.5a36f56a.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=sridhar.samudrala@intel.com \
--cc=virtio-dev@lists.oasis-open.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.