lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250828102656.GY10519@horms.kernel.org>
Date: Thu, 28 Aug 2025 11:26:56 +0100
From: Simon Horman <horms@...nel.org>
To: Alexander Duyck <alexander.duyck@...il.com>
Cc: netdev@...r.kernel.org, kuba@...nel.org, kernel-team@...a.com,
	andrew+netdev@...n.ch, pabeni@...hat.com, davem@...emloft.net
Subject: Re: [net-next PATCH 4/4] fbnic: Push local unicast MAC addresses to
 FW to populate TCAMs

On Tue, Aug 26, 2025 at 12:45:07PM -0700, Alexander Duyck wrote:
> From: Alexander Duyck <alexanderduyck@...com>
> 
> The MACDA TCAM can only be accessed by one entity at a time and as such we
> cannot have simultaneous reads from the firmware to probe for changes from
> the host. As such we have to send a message indicating what the state of
> the MACDA is to the firmware when we updated it so that the firmware can
> sync up the TCAMs it owns to route BMC packets to the host.
> 
> To support that we are adding a new message that is invoked when we write
> the MACDA that will notify the firmware of updates from the host and allow
> it to sync up the TCAM configuration to match the one on the host side.
> 
> Signed-off-by: Alexander Duyck <alexanderduyck@...com>

Reviewed-by: Simon Horman <horms@...nel.org>


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ