[dpdk-dev] [PATCH 00/12] introduce fail-safe PMD
bruce.richardson at intel.com
Fri Mar 3 17:14:20 CET 2017
On Fri, Mar 03, 2017 at 04:40:22PM +0100, Gaetan Rivet wrote:
> This PMD intercepts and manages Ethernet device removal events issued by
> slave PMDs and re-initializes them transparently when brought back so that
> existing applications do not need to be modified to benefit from true
> hot-plugging support.
> The stacked PMD approach shares many similarities with the bonding PMD but
> with a different purpose. While bonding provides the ability to group
> several links into a single logical device for enhanced throughput and
> supports fail-over at link level, this one manages the sudden disappearance
> of the underlying device; it guarantees applications face a valid device in
> working order at all times.
> Each fail-safe instance is configured to run atop one or several
> devices, with one defined as the preferred device. Hot-plug events are
> handled on all of them, and Tx is always directed to the preferred device
> if present or to the next available failover device (Rx is always performed
> on all devices for simplicity).
> Moreover, the configured slaves (preferred or failover) do not need to be
> present at initialization time and may appear later.
> Slaves configuration is continuously synchronized with that of the virtual
> device, which exposes their common set of capabilities to the application.
> Failure to apply the current configuration state to a slave for any reason
> simply reschedules its initialization.
> This series depends on the series
> [PATCH 0/4] clarify eth_dev state management
> [PATCH 0/5] add device removal event
this looks an interesting PMD, and I like the wrapper approach. However,
why duplicate the functionality of the bonding device in another device
driver? Is it not possible to have this driver wrap individual devices
and then have the bonding driver use those wrapped devices to present an
omni-present device? It seems strange to have support for grouping
devices together in two different drivers - one should leverage the
Alternatively, should this be merged into the bonding driver or replace
More information about the dev