[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <62b53e5d-a862-a5a2-88d4-9d10577e4274@mojatatu.com>
Date: Tue, 6 Sep 2016 09:36:57 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Alexei Starovoitov <alexei.starovoitov@...il.com>,
Jiri Pirko <jiri@...nulli.us>,
John Fastabend <john.fastabend@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
netdev@...r.kernel.org, jiri@...lanox.com, idosh@...lanox.com,
john.fastabend@...el.com, ast@...nel.org, davem@...emloft.net,
ecree@...arflare.com, vivien.didelot@...oirfairelinux.com
Subject: Re: Centralizing support for TCAM?
On 16-09-06 09:31 AM, Andrew Lunn wrote:
> So if i'm reading this right, you are talking about big switches, top
> of racks, etc. And you don't see much use for the TCAM.
>
> Florian and I are interested in the other end of the scale. Little
> 5-10 port switches in SoHo, STB, WiFi Access points etc. At the
> moment, firewalling in such devices is done by the CPU. If we can
> offload some of the firewall rules to the TCAM, we would be happy.
>
As with all discussions on netdev, that was a distraction;->
Use tc as mentioned by Jiri. Please please no ethtool.
cheers,
jamal
Powered by blists - more mailing lists