Re: [dpdk-dev] [RFC v2] ethdev: add flow metadata

2018-08-23 Thread Yongseok Koh
> On Aug 20, 2018, at 8:45 AM, Ferruh Yigit wrote: > > On 6/26/2018 9:54 AM, Xueming Li wrote: >> Currently, rte_flow pattern only match packet header fields. >> This patch adds additional data to match the packet. >> >> For example, in egress direction, to do an action depending on the VM >> i

Re: [dpdk-dev] [RFC v2] ethdev: add flow metadata

2018-08-20 Thread Ferruh Yigit
On 8/20/2018 4:45 PM, Ferruh Yigit wrote: > On 6/26/2018 9:54 AM, Xueming Li wrote: >> Currently, rte_flow pattern only match packet header fields. >> This patch adds additional data to match the packet. >> >> For example, in egress direction, to do an action depending on the VM >> id, the applicat

Re: [dpdk-dev] [RFC v2] ethdev: add flow metadata

2018-08-20 Thread Ferruh Yigit
On 6/26/2018 9:54 AM, Xueming Li wrote: > Currently, rte_flow pattern only match packet header fields. > This patch adds additional data to match the packet. > > For example, in egress direction, to do an action depending on the VM > id, the application needs to configure rte_flow rule with the ne

[dpdk-dev] [RFC v2] ethdev: add flow metadata

2018-06-26 Thread Xueming Li
Currently, rte_flow pattern only match packet header fields. This patch adds additional data to match the packet. For example, in egress direction, to do an action depending on the VM id, the application needs to configure rte_flow rule with the new metadata pattern: pattern meta data is {vm}