All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, edumazet@google.com,
	alexander.h.duyck@intel.com, stephen@networkplumber.org,
	daniel@iogearbox.net, mlxsw@mellanox.com
Subject: Re: [patch net-next 0/6] introduce trap control action to tc and offload it
Date: Mon, 5 Jun 2017 21:43:17 +0200	[thread overview]
Message-ID: <20170605194317.GA1986@nanopsycho> (raw)
In-Reply-To: <20170605154651.GE11772@lunn.ch>

Mon, Jun 05, 2017 at 05:46:51PM CEST, andrew@lunn.ch wrote:
>On Mon, Jun 05, 2017 at 04:38:26PM +0200, Jiri Pirko wrote:
>> From: Jiri Pirko <jiri@mellanox.com>
>> 
>> This patchset introduces a control action dedicated to indicate
>> to trap the matched packet to CPU. This is specific action for
>> HW offloads. Also, the patchset offloads the action to mlxsw driver.
>> 
>> Example usage:
>> $ tc filter add dev enp3s0np19 parent ffff: protocol ip prio 20 flower skip_sw dst_ip 192.168.10.1 action trap
>
>Hi Jiri
>
>So i assume this means a frame ingressing on the switch port
>enp3s0np19 matching the filter is now visible on the linux enp3s0np19

Yes.


>interface?  How do you avoid Linux processing it? If enp3s0np19 is a

On contrary. I want Linux to process it. The packet was stolen from the
offloaded fastpath to kernel.


>member of a bridge, we don't want the software bridge processing it
>and forwarding it out another port, since i assume the hardware has
>already done this. Or does the trap stop further processing of the
>frame by the hardware?

Exactly the latter :) Thanks!


>
>Thanks
>      Andrew

  reply	other threads:[~2017-06-05 19:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 14:38 [patch net-next 0/6] introduce trap control action to tc and offload it Jiri Pirko
2017-06-05 14:38 ` [patch net-next 1/6] net: sched: introduce a TRAP control action Jiri Pirko
2017-06-05 19:56   ` Andrew Lunn
2017-06-05 19:59     ` Jiri Pirko
2017-06-05 14:38 ` [patch net-next 2/6] net: sched: introduce helper to identify gact trap action Jiri Pirko
2017-06-05 14:38 ` [patch net-next 3/6] mlxsw: pci: Fix size of trap_id field in CQE Jiri Pirko
2017-06-05 14:38 ` [patch net-next 4/6] mlxsw: spectrum: Introduce ACL trap Jiri Pirko
2017-06-05 14:38 ` [patch net-next 5/6] acl: Introduce ACL trap action Jiri Pirko
2017-06-05 14:38 ` [patch net-next 6/6] spectrum_flower: Implement gact trap TC action offload Jiri Pirko
2017-06-05 14:39 ` [patch iproute2/net-next] tc: add support for TRAP action Jiri Pirko
2017-06-08  6:57   ` Jiri Pirko
2017-06-08 17:26   ` Jiri Benc
2017-06-08 18:41     ` Jiri Pirko
2017-06-08 18:03   ` Stephen Hemminger
2017-06-05 15:46 ` [patch net-next 0/6] introduce trap control action to tc and offload it Andrew Lunn
2017-06-05 19:43   ` Jiri Pirko [this message]
2017-06-05 19:56     ` Jiri Pirko

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=20170605194317.GA1986@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=alexander.h.duyck@intel.com \
    --cc=andrew@lunn.ch \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=xiyou.wangcong@gmail.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.