From: Jiri Pirko <jiri@resnulli.us>
To: Sridhar Samudrala <sridhar.samudrala@intel.com>
Cc: mst@redhat.com, stephen@networkplumber.org, davem@davemloft.net,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org,
virtio-dev@lists.oasis-open.org, jesse.brandeburg@intel.com,
alexander.h.duyck@intel.com, kubakici@wp.pl, jasowang@redhat.com,
loseweigh@gmail.com, aaron.f.brown@intel.com,
anjali.singhai@intel.com
Subject: Re: [PATCH net-next v11 3/5] net: Introduce net_failover driver
Date: Tue, 22 May 2018 10:59:40 +0200 [thread overview]
Message-ID: <20180522085940.GD2149@nanopsycho> (raw)
In-Reply-To: <1526954781-35359-4-git-send-email-sridhar.samudrala@intel.com>
Tue, May 22, 2018 at 04:06:19AM CEST, sridhar.samudrala@intel.com wrote:
>The net_failover driver provides an automated failover mechanism via APIs
>to create and destroy a failover master netdev and mananges a primary and
>standby slave netdevs that get registered via the generic failover
>infrastructure.
>
>The failover netdev acts a master device and controls 2 slave devices. The
>original paravirtual interface gets registered as 'standby' slave netdev and
>a passthru/vf device with the same MAC gets registered as 'primary' slave
>netdev. Both 'standby' and 'failover' netdevs are associated with the same
>'pci' device. The user accesses the network interface via 'failover' netdev.
>The 'failover' netdev chooses 'primary' netdev as default for transmits when
>it is available with link up and running.
>
>This can be used by paravirtual drivers to enable an alternate low latency
>datapath. It also enables hypervisor controlled live migration of a VM with
>direct attached VF by failing over to the paravirtual datapath when the VF
>is unplugged.
>
>Signed-off-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
[...]
>+
>+The net_failover driver provides an automated failover mechanism via APIs
>+to create and destroy a failover master netdev and mananges a primary and
s/mananges/manages/
next prev parent reply other threads:[~2018-05-22 8:59 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 2:06 [virtio-dev] [PATCH net-next v11 0/5] Enable virtio_net to act as a standby for a passthru device Sridhar Samudrala
2018-05-22 2:06 ` Sridhar Samudrala
2018-05-22 2:06 ` [PATCH net-next v11 1/5] net: Introduce generic failover module Sridhar Samudrala
2018-05-22 2:06 ` [virtio-dev] " Sridhar Samudrala
2018-05-22 2:06 ` Sridhar Samudrala
2018-05-22 2:06 ` [virtio-dev] [PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework Sridhar Samudrala
2018-05-22 2:06 ` Sridhar Samudrala
2018-05-22 9:06 ` Jiri Pirko
2018-05-22 9:08 ` Jiri Pirko
2018-05-22 9:08 ` Jiri Pirko
2018-05-22 13:12 ` Michael S. Tsirkin
2018-05-22 13:12 ` [virtio-dev] " Michael S. Tsirkin
2018-05-22 13:12 ` Michael S. Tsirkin
2018-05-22 13:14 ` Jiri Pirko
2018-05-22 13:14 ` Jiri Pirko
2018-05-22 13:17 ` [virtio-dev] " Michael S. Tsirkin
2018-05-22 13:17 ` Michael S. Tsirkin
2018-05-22 13:26 ` Jiri Pirko
2018-05-22 13:26 ` Jiri Pirko
2018-05-22 13:39 ` Michael S. Tsirkin
2018-05-22 13:39 ` [virtio-dev] " Michael S. Tsirkin
2018-05-22 13:39 ` Michael S. Tsirkin
2018-05-22 15:13 ` Jiri Pirko
2018-05-22 15:13 ` Jiri Pirko
2018-05-22 15:32 ` Michael S. Tsirkin
2018-05-22 15:32 ` [virtio-dev] " Michael S. Tsirkin
2018-05-22 15:32 ` Michael S. Tsirkin
2018-05-22 15:45 ` Jiri Pirko
2018-05-22 16:52 ` Michael S. Tsirkin
2018-05-22 16:52 ` [virtio-dev] " Michael S. Tsirkin
2018-05-22 16:52 ` Michael S. Tsirkin
2018-05-22 17:38 ` Jiri Pirko
2018-05-22 19:54 ` Michael S. Tsirkin
2018-05-22 19:54 ` [virtio-dev] " Michael S. Tsirkin
2018-05-22 19:54 ` Michael S. Tsirkin
2018-05-22 17:38 ` Jiri Pirko
2018-05-22 13:17 ` Michael S. Tsirkin
2018-05-22 15:28 ` Samudrala, Sridhar
2018-05-22 15:28 ` [virtio-dev] " Samudrala, Sridhar
2018-05-22 15:28 ` Samudrala, Sridhar
2018-05-22 15:36 ` Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future Jiri Pirko
2018-05-22 15:46 ` [virtio-dev] " Michael S. Tsirkin
2018-05-22 15:46 ` Michael S. Tsirkin
2018-05-22 16:12 ` [PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework Jiri Pirko
2018-05-22 20:54 ` [virtio-dev] " Samudrala, Sridhar
2018-05-22 20:54 ` Samudrala, Sridhar
2018-05-23 6:27 ` Jiri Pirko
2018-05-23 6:27 ` Jiri Pirko
2018-05-23 16:16 ` Samudrala, Sridhar
2018-05-23 16:16 ` [virtio-dev] " Samudrala, Sridhar
2018-05-23 16:16 ` Samudrala, Sridhar
2018-05-22 20:54 ` Samudrala, Sridhar
2018-05-22 16:12 ` Jiri Pirko
2018-05-22 15:46 ` Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future Michael S. Tsirkin
2018-05-22 15:36 ` Jiri Pirko
2018-05-22 9:06 ` [PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework Jiri Pirko
2018-05-22 2:06 ` Sridhar Samudrala
2018-05-22 2:06 ` [PATCH net-next v11 3/5] net: Introduce net_failover driver Sridhar Samudrala
2018-05-22 2:06 ` [virtio-dev] " Sridhar Samudrala
2018-05-22 2:06 ` Sridhar Samudrala
2018-05-22 8:59 ` Jiri Pirko
2018-05-22 8:59 ` Jiri Pirko [this message]
2018-05-22 2:06 ` [PATCH net-next v11 4/5] virtio_net: Introduce VIRTIO_NET_F_STANDBY feature bit Sridhar Samudrala
2018-05-22 2:06 ` [virtio-dev] " Sridhar Samudrala
2018-05-22 2:06 ` Sridhar Samudrala
2018-05-22 2:06 ` [virtio-dev] [PATCH net-next v11 5/5] virtio_net: Extend virtio to use VF datapath when available Sridhar Samudrala
2018-05-22 2:06 ` Sridhar Samudrala
2018-05-22 2:06 ` Sridhar Samudrala
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=20180522085940.GD2149@nanopsycho \
--to=jiri@resnulli.us \
--cc=aaron.f.brown@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=anjali.singhai@intel.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=kubakici@wp.pl \
--cc=loseweigh@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=stephen@networkplumber.org \
--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 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.