[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7152c343-63e6-aa7f-82c7-ad63725c3bc8@mellanox.com>
Date: Sun, 16 Jun 2019 07:29:59 +0000
From: Paul Blakey <paulb@...lanox.com>
To: Cong Wang <xiyou.wangcong@...il.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" <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 6/14/2019 9:02 PM, Cong Wang wrote:
> 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.
Sure I'll add that.
Powered by blists - more mailing lists