On Mon, 29 May 2017 15:42:19 +0200 Gaetan Rivet <gaetan.ri...@6wind.com> wrote:
> Signed-off-by: Gaetan Rivet <gaetan.ri...@6wind.com> > Acked-by: Olga Shern <ol...@mellanox.com> > --- > doc/guides/nics/features/failsafe.ini | 1 + > drivers/net/failsafe/Makefile | 1 + > drivers/net/failsafe/failsafe.c | 1 + > drivers/net/failsafe/failsafe_eal.c | 1 + > drivers/net/failsafe/failsafe_ether.c | 70 +++++++++++ > drivers/net/failsafe/failsafe_flow.c | 216 > ++++++++++++++++++++++++++++++++ > drivers/net/failsafe/failsafe_ops.c | 29 +++++ > drivers/net/failsafe/failsafe_private.h | 18 +++ > 8 files changed, 337 insertions(+) > create mode 100644 drivers/net/failsafe/failsafe_flow.c How does this interact with typical case of VF and dumb virtual device? The VF has flow API but dumb virtual device does not. How does this work with late binding plugin? If VF arrives later is the flow table reprogrammed to the VF?
