All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>,
	John Fastabend <john.fastabend@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	netdev@vger.kernel.org, jiri@mellanox.com, idosh@mellanox.com,
	john.fastabend@intel.com, ast@kernel.org, davem@davemloft.net,
	ecree@solarflare.com, vivien.didelot@savoirfairelinux.com
Subject: Re: Centralizing support for TCAM?
Date: Tue, 6 Sep 2016 09:36:57 -0400	[thread overview]
Message-ID: <62b53e5d-a862-a5a2-88d4-9d10577e4274@mojatatu.com> (raw)
In-Reply-To: <20160906133105.GD2719@lunn.ch>

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

      reply	other threads:[~2016-09-06 13:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57d4a2db-ca3b-909a-073a-52ecceb428f2@gmail.com>
2016-09-02 17:18 ` Centralizing support for TCAM? Florian Fainelli
2016-09-02 18:49   ` John Fastabend
2016-09-02 19:02     ` Andrew Lunn
2016-09-03  7:09     ` Jiri Pirko
2016-09-06  3:44       ` Alexei Starovoitov
2016-09-06 11:17         ` Jamal Hadi Salim
2016-09-06 13:31           ` Andrew Lunn
2016-09-06 13:36             ` Jamal Hadi Salim [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62b53e5d-a862-a5a2-88d4-9d10577e4274@mojatatu.com \
    --to=jhs@mojatatu.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=ast@kernel.org \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=f.fainelli@gmail.com \
    --cc=idosh@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=jiri@resnulli.us \
    --cc=john.fastabend@gmail.com \
    --cc=john.fastabend@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.