[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpXQgJti9faPA5kVV7Ly3LStHf3zwDP5S-PfBz2jR0Y8xA@mail.gmail.com>
Date: Fri, 14 Jun 2019 11:02:48 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Paul Blakey <paulb@...lanox.com>
Cc: Jiri Pirko <jiri@...lanox.com>, Roi Dayan <roid@...lanox.com>,
Yossi Kuperman <yossiku@...lanox.com>,
Oz Shlomo <ozsh@...lanox.com>,
Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Aaron Conole <aconole@...hat.com>,
Zhike Wang <wangzhike@...com>,
Rony Efraim <ronye@...lanox.com>, nst-kernel@...hat.com,
John Hurley <john.hurley@...ronome.com>,
Simon Horman <simon.horman@...ronome.com>,
Justin Pettit <jpettit@....org>
Subject: Re: [PATCH net-next 1/3] net/sched: Introduce action ct
On Tue, Jun 11, 2019 at 7:05 AM Paul Blakey <paulb@...lanox.com> wrote:
>
> Allow sending a packet to conntrack and set conntrack zone, mark,
> labels and nat parameters.
>
This is too short to justify why you want to play with L3 stuff in L2.
Please be as specific as you can.
Also, please document its use case too.
Thanks.
Powered by blists - more mailing lists