[dpdk-dev] [PATCH 2/2] examples/ipsec-secgw: add target queues in flow actions
Nelio Laranjeiro
nelio.laranjeiro at 6wind.com
Fri Dec 1 17:26:17 CET 2017
Hi Annob
On Fri, Dec 01, 2017 at 08:34:04PM +0530, Anoob Joseph wrote:
<snip>
> >
> > I think we have an agreement here, in order the final action to be
> > tested:
> >
> > 1. PASSTHRU
> > 2. RSS
> > 3. QUEUE
> >
> > If those 3 fails, the functions fails to create the rule, the first
> > succeeding is the one applied.
> PASSTHRU itself is non-terminating, right? So I'm not sure, how a check with
> PASSTHRU would help us. SECURITY will be terminating action on Cavium
> hardware. So, the first check could be without any addition. If that fails,
> RSS. And then QUEUE. That should be fine.
Agreed, assuming PASSTHRU [1] is not mandatory (i.e. explicit) when the
rule action list is not terminal.
A small suggestion, you should accept/ignore such action in your PMD,
the API also allows applications to add it.
Thanks,
[1] http://dpdk.org/doc/guides/prog_guide/rte_flow.html#action-types
--
Nélio Laranjeiro
6WIND
More information about the dev
mailing list