: Wednesday, August 29, 2018 3:07 PM
To: Dekel Peled
Cc: Yongseok Koh ; dev ; Shahaf Shuler
; Ori Kam ; Andrew Rybchenko
; Yigit, Ferruh ; Thomas
Monjalon ; Ananyev, Konstantin
; Adrien Mazarguil ;
Olivier Matz ; Alex Rosenbaum
Subject: Re: [dpdk-dev] [RFC v2] ethdev: support metadata as flow
Hi Dekel,
Could you please show with an example i.e how the corresponding
'flow create' cmd will look like in testpmd?
Also I'm guessing you would need to change the cmdline_parser logic in
testpmd application as well to recognize this new rte_flow_item?
Thanks
Som
On Wed, Aug 29, 2018 at
> -Original Message-
> From: Yongseok Koh
> Sent: Tuesday, August 28, 2018 10:44 PM
> To: Dekel Peled
> Cc: dev ; Shahaf Shuler ; Ori Kam
> ; Andrew Rybchenko ;
> Yigit, Ferruh ; Thomas Monjalon
> ; Ananyev, Konstantin
> ; Adrien Mazarguil
> ; Olivier Matz ;
> Alex Rosenbaum
> Subject:
> On Aug 26, 2018, at 7:09 AM, Dekel Peled wrote:
>
> Current implementation of rte_flow allows match pattern of flow rule,
> based on packet data or header fields.
> This limits the application use of match patterns.
>
> For example, consider a vswitch application which controls a set of VMs,
>
Current implementation of rte_flow allows match pattern of flow rule,
based on packet data or header fields.
This limits the application use of match patterns.
For example, consider a vswitch application which controls a set of VMs,
connected with virtio, in a fabric with overlay of VXLAN.
Several
5 matches
Mail list logo
