On Wed, Oct 30, 2019 at 03:58:04PM +, Slava Ovsiienko wrote:
> > -Original Message-
> > From: Olivier Matz
> > Sent: Wednesday, October 30, 2019 17:20
> > To: Slava Ovsiienko
> > Cc: Andrew Rybchenko ; dev@dpdk.org;
> > Matan Azrad ; Raslan Darawsheh
> > ; Thomas Monjalon
> > Subject
> -Original Message-
> From: Olivier Matz
> Sent: Wednesday, October 30, 2019 17:20
> To: Slava Ovsiienko
> Cc: Andrew Rybchenko ; dev@dpdk.org;
> Matan Azrad ; Raslan Darawsheh
> ; Thomas Monjalon
> Subject: Re: [PATCH v5] ethdev: extend flow metadata
>
> Hi,
>
> On Wed, Oct 30, 2019
30/10/2019 16:20, Olivier Matz:
> > From: Slava Ovsiienko
> > > > On 10/29/19 10:31 PM, Viacheslav Ovsiienko wrote:
> > > > > Currently, metadata can be set on egress path via mbuf tx_metadata
> > > > > field with PKT_TX_METADATA flag and RTE_FLOW_ITEM_TYPE_META
> > > > matches metadata.
> > > > >
Hi,
On Wed, Oct 30, 2019 at 02:46:06PM +, Slava Ovsiienko wrote:
> > -Original Message-
> > From: Slava Ovsiienko
> > Sent: Wednesday, October 30, 2019 16:41
> > To: Andrew Rybchenko ; dev@dpdk.org
> > Cc: Matan Azrad ; Raslan Darawsheh
> > ; Thomas Monjalon ;
> > olivier.m...@6wind.co
> -Original Message-
> From: Slava Ovsiienko
> Sent: Wednesday, October 30, 2019 16:41
> To: Andrew Rybchenko ; dev@dpdk.org
> Cc: Matan Azrad ; Raslan Darawsheh
> ; Thomas Monjalon ;
> olivier.m...@6wind.com
> Subject: RE: [PATCH v5] ethdev: extend flow metadata
>
> > -Original Messag
> -Original Message-
> From: Andrew Rybchenko
> Sent: Wednesday, October 30, 2019 10:02
> To: Slava Ovsiienko ; dev@dpdk.org
> Cc: Matan Azrad ; Raslan Darawsheh
> ; Thomas Monjalon ;
> olivier.m...@6wind.com; Yongseok Koh
> Subject: Re: [PATCH v5] ethdev: extend flow metadata
>
> On 10/
Subject: [dpdk-dev] [PATCH v5] ethdev: extend flow metadata
>
> Currently, metadata can be set on egress path via mbuf tx_metadata field
> with PKT_TX_METADATA flag and RTE_FLOW_ITEM_TYPE_META matches
> metadata.
>
> This patch extends the metadata feature usability.
>
> 1)
On 10/29/19 10:31 PM, Viacheslav Ovsiienko wrote:
Currently, metadata can be set on egress path via mbuf tx_metadata field
with PKT_TX_METADATA flag and RTE_FLOW_ITEM_TYPE_META matches metadata.
This patch extends the metadata feature usability.
1) RTE_FLOW_ACTION_TYPE_SET_META
When supporting
Currently, metadata can be set on egress path via mbuf tx_metadata field
with PKT_TX_METADATA flag and RTE_FLOW_ITEM_TYPE_META matches metadata.
This patch extends the metadata feature usability.
1) RTE_FLOW_ACTION_TYPE_SET_META
When supporting multiple tables, Tx metadata can also be set by a r
9 matches
Mail list logo
