From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-4853-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id D7A24985CEE for ; Tue, 18 Sep 2018 10:20:59 +0000 (UTC) Date: Tue, 18 Sep 2018 12:20:52 +0200 From: Cornelia Huck Message-ID: <20180918122052.349ba42e.cohuck@redhat.com> In-Reply-To: <20180912111819-mutt-send-email-mst@kernel.org> References: <1534358955-35869-1-git-send-email-sridhar.samudrala@intel.com> <20180907173251-mutt-send-email-mst@kernel.org> <9bc2db49-77ea-1391-b964-a29da44ff617@intel.com> <20180912111819-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [virtio-dev] [PATCH v4] content: Introduce VIRTIO_NET_F_STANDBY feature To: "Michael S. Tsirkin" Cc: "Samudrala, Sridhar" , virtio-dev@lists.oasis-open.org List-ID: On Wed, 12 Sep 2018 11:22:12 -0400 "Michael S. Tsirkin" wrote: > On Wed, Sep 12, 2018 at 08:17:45AM -0700, Samudrala, Sridhar wrote: > > > > > > On 9/7/2018 2:34 PM, Michael S. Tsirkin wrote: > > > On Wed, Aug 15, 2018 at 11:49:15AM -0700, Sridhar Samudrala wrote: > > > > VIRTIO_NET_F_STANDBY feature enables hypervisor to indicate virtio_net > > > > device to act as a standby for another device with the same MAC address. > > > > > > > > Signed-off-by: Sridhar Samudrala > > > > Acked-by: Cornelia Huck > > > > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/18 > > > Applied but when do you plan to add documentation as pointed > > > out by Jan and Halil? > > > > I thought additional documentation will be done as part of the Qemu enablement > > patches and i hope someone in RH is looking into it. > > > > Does it make sense to add a link to to the kernel documentation of this feature in > > the spec > > https://www.kernel.org/doc/html/latest/networking/net_failover.html > > > I do not think this will address the comments posted. Specifically we > should probably include documentation for what is a standby and primary: > what is expected of driver (maintain configuration on standby, support > primary coming and going, transmit on standby only if there is no > primary) and of device (have same mac for standby as for standby). Yes, we need some definitive statements of what a driver and a device is supposed to do in order to conform; it might make sense to discuss this in conjunction with discussion on any QEMU patches (have not checked whether anything has been posted, just returned from vacation). I assume that we still stick with the plan to implement/document MAC-based handling first and then enhance with other methods later? --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org