[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240812200437.3581990-1-sean.anderson@linux.dev>
Date: Mon, 12 Aug 2024 16:04:33 -0400
From: Sean Anderson <sean.anderson@...ux.dev>
To: Radhey Shyam Pandey <radhey.shyam.pandey@....com>,
netdev@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
Andrew Lunn <andrew@...n.ch>,
Michal Simek <michal.simek@....com>,
Daniel Borkmann <daniel@...earbox.net>,
Paolo Abeni <pabeni@...hat.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
linux-arm-kernel@...ts.infradead.org,
Jakub Kicinski <kuba@...nel.org>,
Ariane Keller <ariane.keller@....ee.ethz.ch>,
Sean Anderson <sean.anderson@...ux.dev>
Subject: [PATCH net-next 0/4] net: xilinx: axienet: Multicast fixes and improvements
This series has a few small patches improving the handling of multicast
addresses. In particular, it makes the driver a whole lot less spammy,
and adjusts things so we aren't in promiscuous mode when we have more
than four multicast addresses (a common occurance on modern systems).
As the hardware has a 4-entry CAM, the ideal method would be to "pack"
multiple addresses into one CAM entry. Something like:
entry.address = address[0] | address[1];
entry.mask = ~(address[0] ^ address[1]);
Which would make the entry match both addresses (along with some others
that would need to be filtered in software).
Mapping addresses to entries in an efficient way is a bit tricky. If
anyone knows of an in-tree example of something like this, I'd be glad
to hear about it.
Sean Anderson (4):
net: xilinx: axienet: Always disable promiscuous mode
net: xilinx: axienet: Fix dangling multicast addresses
net: xilinx: axienet: Don't print if we go into promiscuous mode
net: xilinx: axienet: Support IFF_ALLMULTI
drivers/net/ethernet/xilinx/xilinx_axienet.h | 3 ++
.../net/ethernet/xilinx/xilinx_axienet_main.c | 52 +++++++++----------
2 files changed, 29 insertions(+), 26 deletions(-)
--
2.35.1.1320.gc452695387.dirty
Powered by blists - more mailing lists