From: Cornelia Huck <cohuck@redhat.com>
To: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>, mst@redhat.com
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] Re: [PATCH v2] content: Introduce VIRTIO_NET_F_STANDBY feature
Date: Wed, 25 Jul 2018 15:02:31 +0200 [thread overview]
Message-ID: <20180725150231.4c8bd3ae.cohuck@redhat.com> (raw)
In-Reply-To: <054ef852-6131-b52d-9ce6-d3f95481ad80@intel.com>
On Tue, 24 Jul 2018 11:27:33 -0700
"Samudrala, Sridhar" <sridhar.samudrala@intel.com> wrote:
> On 7/24/2018 5:43 AM, Cornelia Huck wrote:
> > I still think we need a more detailed description of how this is
> > supposed to work elsewhere (i.e., outside of the normative section).
> > But we can probably merge an updated version of this patch to get at
> > least the feature bit reserved and documented. Thoughts?
>
> Sure. I can submit a v3 version with the minor changes you suggested.
> The detailed description of the failover mechanism can be added once qemu
> patch to handle the standby feature bit is submitted and reviewed.
> I am assuming someone in RH is looking into the qemu enablement patch.
Sounds reasonable to me.
Michael, what do you think?
---------------------------------------------------------------------
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-25 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 17:02 [virtio-dev] [PATCH v2] content: Introduce VIRTIO_NET_F_STANDBY feature Sridhar Samudrala
2018-07-24 12:43 ` [virtio-dev] " Cornelia Huck
2018-07-24 18:27 ` Samudrala, Sridhar
2018-07-25 13:02 ` Cornelia Huck [this message]
2018-07-25 13:27 ` Michael S. Tsirkin
2018-07-25 23:31 ` Siwei Liu
2018-07-26 8:48 ` Cornelia Huck
2018-07-26 20:24 ` Siwei Liu
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=20180725150231.4c8bd3ae.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox