[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Feb 2017 11:16:43 +0100
From: Simon Horman <simon.horman@...ronome.com>
To: Yotam Gigi <yotamg@...lanox.com>
Cc: jhs@...atatu.com, davem@...emloft.net, netdev@...r.kernel.org,
jiri@...lanox.com, eladr@...lanox.com, idosch@...lanox.com
Subject: Re: [PATCH net-next 0/2] Extract IFE logic to module
Hi Yotam,
On Tue, Jan 31, 2017 at 03:57:02PM +0200, Yotam Gigi wrote:
> Extract ife logic from the tc_ife action into an independent module, and
> make the tc_ife action use it. This way, the ife encapsulation can be used
> by other modules other than tc_ife action.
I have no objection to this modularisation but I am curious to know
if you have a use-case in mind. My understanding is that earlier versions
of the sample action used IFE but that is not the case in the version that
was ultimately accepted.
Powered by blists - more mailing lists