Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 7 Jul 2021 16:56:25 +0200
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
Message-ID: <YOXAmZXIPukotquk@lunn.ch>
References: <20210706011548.2201-1-callum.sinclair@alliedtelesis.co.nz>
 <YORaY83GiD56/su0@lunn.ch>
 <1625623229789.98509@alliedtelesis.co.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1625623229789.98509@alliedtelesis.co.nz>
Precedence: bulk

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