netdev - Re: [PATCH net-next v2] eth: fbnic: Add support to write TCE TCAM entries

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] [day] [month] [year] [list]

Message-ID: <5b6032d7-58f6-4e2d-98ec-68f7f55ae2c1@gmail.com>
Date: Wed, 30 Oct 2024 18:19:45 -0700
From: Mohsin Bashir <mohsin.bashr@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, alexanderduyck@...com, kuba@...nel.org,
 andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
 pabeni@...hat.com, kernel-team@...a.com, sanmanpradhan@...a.com,
 sdf@...ichev.me, vadim.fedorenko@...ux.dev, hmohsin@...a.com
Subject: Re: [PATCH net-next v2] eth: fbnic: Add support to write TCE TCAM
 entries

Hi Andrew,

Basically, in addition to the RX TCAM (RPC) that you mentioned, we also 
have a TCAM on the TX path that enables traffic redirection for BMC. 
Unlike other NICs where BMC diversion is typically handled by firmware, 
FBNIC firmware does not touch anything host-related. In this patch, we 
are writing MACDA entries from the RPC (Rx Parser and Classifier) to the 
TX TCAM, allowing us to reroute any host traffic destined for BMC.

I will ensure that the commit message for the revised version clearly 
explains this.

On 10/30/24 11:34 AM, Andrew Lunn wrote:
> On Thu, Oct 24, 2024 at 03:31:35PM -0700, Mohsin Bashir wrote:
>> Add support for writing to the tce tcam to enable host to bmc traffic.
> 
> The commit message is not really helping me understand what is going
> on here. What entries are you adding to the TCAM? Normally a TCAM is
> used on ingress, but you are talking about host to BMC, which is
> egress?
> 
> 	Andrew