; shah...@mellanox.com;
tho...@monjalon.net; Yigit, Ferruh
; adrien.mazarg...@6wind.com; olivier.m...@6wind.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC 1/3] ethdev: extend flow metadata
On 6/4/19 12:32 AM, Yongseok Koh wrote:
Currently, metadata can be set on egress path via mbuf
> > > To: Yongseok Koh ; shah...@mellanox.com;
> > > tho...@monjalon.net; Yigit, Ferruh
> > > ; adrien.mazarg...@6wind.com;
> > > olivier.m...@6wind.com
> > > Cc: dev@dpdk.org
> > > Subject: Re: [dpdk-dev] [RFC 1/3] ethdev: extend flow metadata
> >
...@6wind.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC 1/3] ethdev: extend flow metadata
On 6/4/19 12:32 AM, Yongseok Koh wrote:
Currently, metadata can be set on egress path via mbuf tx_meatadata field
with PKT_TX_METADATA flag and RTE_FLOW_ITEM_TYPE_RX_META matches metadata.
This patch extends the
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [RFC 1/3] ethdev: extend flow metadata
>
> On 6/4/19 12:32 AM, Yongseok Koh wrote:
> > Currently, metadata can be set on egress path via mbuf tx_meatadata field
> > with PKT_TX_METADATA flag and RTE_FLOW_ITEM_TYPE_RX_META matches metadata
On 6/4/19 12:32 AM, Yongseok Koh wrote:
Currently, metadata can be set on egress path via mbuf tx_meatadata field
with PKT_TX_METADATA flag and RTE_FLOW_ITEM_TYPE_RX_META matches metadata.
This patch extends the usability.
1) RTE_FLOW_ACTION_TYPE_SET_META
When supporting multiple tables, Tx me
Currently, metadata can be set on egress path via mbuf tx_meatadata field
with PKT_TX_METADATA flag and RTE_FLOW_ITEM_TYPE_RX_META matches metadata.
This patch extends the usability.
1) RTE_FLOW_ACTION_TYPE_SET_META
When supporting multiple tables, Tx metadata can also be set by a rule and
match
6 matches
Mail list logo
