netdev - Re: [PATCH net-next] rocker: forward packets to CPU when port is joined to openvswitch

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]

Date:	Wed, 15 Jul 2015 23:40:31 -0700
From:	Scott Feldman <sfeldma@...il.com>
To:	Simon Horman <simon.horman@...ronome.com>
Cc:	Jiri Pirko <jiri@...nulli.us>, David Miller <davem@...emloft.net>,
	Netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next] rocker: forward packets to CPU when port is
 joined to openvswitch

On Wed, Jul 15, 2015 at 6:39 PM, Simon Horman
<simon.horman@...ronome.com> wrote:
> Teach rocker to forward packets to CPU when a port is joined to Open vSwitch.
> There is scope to later refine what is passed up as per Open vSwitch flows
> on a port.
>
> This does not change the behaviour of rocker ports that are
> not joined to Open vSwitch.
>
> Signed-off-by: Simon Horman <simon.horman@...ronome.com>

Acked-by: Scott Feldman <sfeldma@...il.com>

Now, OVS flows on a port.  Strange enough, that was the first RFC
implementation for switchdev/rocker where we hooked into ovs-kernel
module and programmed flows into hw.  We pulled all of that code
because, IIRC, the ovs folks didn't want us hooking into the kernel
module directly.  We dropped the ovs hooks and focused on hooking
kernel's L2/L3.  The device (rocker) didn't really change: OF-DPA
pipeline was used for both.  Might be interesting to try hooking it
again.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html