From: Andrew Lunn <andrew@lunn.ch>
To: Callum Sinclair <Callum.Sinclair@alliedtelesis.co.nz>
Cc: "dsahern@kernel.org" <dsahern@kernel.org>,
"nikolay@nvidia.com" <nikolay@nvidia.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linus.luessing@c0d3.blue" <linus.luessing@c0d3.blue>
Subject: Re: [PATCH] net: Allow any address multicast join for IP sockets
Date: Wed, 7 Jul 2021 16:56:25 +0200 [thread overview]
Message-ID: <YOXAmZXIPukotquk@lunn.ch> (raw)
In-Reply-To: <1625623229789.98509@alliedtelesis.co.nz>
On Wed, Jul 07, 2021 at 02:00:29AM +0000, Callum Sinclair wrote:
> Hi Andrew
>
> Yes I want to receive all multicast frames.This is to configure
> a userspace switch driver to prevent unknown multicast
> routes being flooded unexpectedly to all switch ports.
Don't you just need the signalling, not the data?
Also, netdev is not friendly to user space switch drivers. You should
be using an in kernel switch driver. So we are unlikely to add an API
which is only going to be used by a user space switch driver. If you
provide patches to mrouted, or frr pim routing daemon which makes use
of this new API, it might get accepted, and then you can also use it
in your user space switch driver as well. Otherwise, i would suggest
you keep to the existing APIs, BPF and pcap for example.
Andrew
prev parent reply other threads:[~2021-07-07 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 1:15 [PATCH] net: Allow any address multicast join for IP sockets Callum Sinclair
2021-07-06 1:15 ` Callum Sinclair
2021-07-06 5:18 ` kernel test robot
2021-07-07 7:26 ` [kbuild] " Dan Carpenter
2021-07-06 13:28 ` Andrew Lunn
2021-07-07 2:00 ` Callum Sinclair
2021-07-07 14:56 ` Andrew Lunn [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=YOXAmZXIPukotquk@lunn.ch \
--to=andrew@lunn.ch \
--cc=Callum.Sinclair@alliedtelesis.co.nz \
--cc=dsahern@kernel.org \
--cc=linus.luessing@c0d3.blue \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.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).