From: Stephen Hemminger <stephen@networkplumber.org>
To: Andrew Rybchenko <arybchenko@solarflare.com>
Cc: Gaetan Rivet <gaetan.rivet@6wind.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 0/2] net/failsafe: support multicast MAC address set
Date: Fri, 21 Sep 2018 09:43:33 -0700 [thread overview]
Message-ID: <20180921094333.0c1e0fa3@xeon-e3> (raw)
In-Reply-To: <c63e428b-1cbc-8976-e9db-98a61f0d0297@solarflare.com>
On Fri, 21 Sep 2018 19:33:16 +0300
Andrew Rybchenko <arybchenko@solarflare.com> wrote:
> On 9/21/18 7:21 PM, Stephen Hemminger wrote:
> > On Fri, 21 Sep 2018 16:36:19 +0100
> > Andrew Rybchenko <arybchenko@solarflare.com> wrote:
> >
> >> v3:
> >> - move apply on sync to fs_eth_dev_conf_apply() to apply to
> >> a new subdevice only
> >> - use ethdev API to apply to sub-device on sync
> >> - remove unnecessary check the same pointer from the method
> >> implementation in failsafe
> >>
> >> v2:
> >> - fix setting of zero addresses since rte_realloc() returns NULL
> >>
> >> Evgeny Im (2):
> >> net/failsafe: remove not supported multicast MAC filter
> >> net/failsafe: support multicast address list set
> >>
> >> doc/guides/rel_notes/release_18_11.rst | 1 +
> >> drivers/net/failsafe/failsafe.c | 1 +
> >> drivers/net/failsafe/failsafe_ether.c | 17 +++++++++
> >> drivers/net/failsafe/failsafe_ops.c | 50 +++++++++++++++++++++++++
> >> drivers/net/failsafe/failsafe_private.h | 2 +
> >> 5 files changed, 71 insertions(+)
> >>
> > Since TAP has no filtering this doesn't really do much for the slowpath.
>
> Yes, I know that TAP does not support it. Is failsafe so tighly bound to
> TAP to block it?
>
failsafe was built to be used with tap and mlx on Azure.
It could be used with virtio and other NIC on KVM, but this is mostly theoretical.
prev parent reply other threads:[~2018-09-21 16:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 15:53 [dpdk-dev] [PATCH " Andrew Rybchenko
2018-08-31 15:53 ` [dpdk-dev] [PATCH 1/2] net/failsafe: remove not supported multicast MAC filter Andrew Rybchenko
2018-08-31 15:53 ` [dpdk-dev] [PATCH 2/2] net/failsafe: support multicast address list set Andrew Rybchenko
2018-09-03 6:47 ` Andrew Rybchenko
2018-09-03 6:55 ` [dpdk-dev] [PATCH v2 0/2] net/failsafe: support multicast MAC address set Andrew Rybchenko
2018-09-03 6:55 ` [dpdk-dev] [PATCH v2 1/2] net/failsafe: remove not supported multicast MAC filter Andrew Rybchenko
2018-09-03 6:55 ` [dpdk-dev] [PATCH v2 2/2] net/failsafe: support multicast address list set Andrew Rybchenko
2018-09-19 14:50 ` Gaëtan Rivet
2018-09-19 15:12 ` Gaëtan Rivet
2018-09-20 11:46 ` Andrew Rybchenko
2018-09-21 15:36 ` [dpdk-dev] [PATCH v3 0/2] net/failsafe: support multicast MAC address set Andrew Rybchenko
2018-09-21 15:36 ` Andrew Rybchenko
2018-09-21 16:09 ` Gaëtan Rivet
2018-09-24 15:58 ` Ferruh Yigit
2018-09-21 15:36 ` [dpdk-dev] [PATCH v3 1/2] net/failsafe: remove not supported multicast MAC filter Andrew Rybchenko
2018-09-21 15:36 ` [dpdk-dev] [PATCH v3 2/2] net/failsafe: support multicast address list set Andrew Rybchenko
2018-09-21 16:21 ` [dpdk-dev] [PATCH v3 0/2] net/failsafe: support multicast MAC address set Stephen Hemminger
2018-09-21 16:33 ` Andrew Rybchenko
2018-09-21 16:38 ` Andrew Rybchenko
2018-09-21 16:43 ` Stephen Hemminger [this message]
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=20180921094333.0c1e0fa3@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
/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;
as well as URLs for NNTP newsgroup(s).