; dev@dpdk.org; or...@mellanox.com;
>> shah...@mellanox.com; Thomas Monjalon
>> ; Ananyev, Konstantin ;
>> Yigit, Ferruh ; Adrien
>> Mazarguil ; Olivier Matz
>> Subject: Re: [dpdk-dev] [RFC] ethdev: support metadata as flow rule criteria
>>
>> On Wed, Aug 22, 2018
; Yigit, Ferruh ; Adrien
> Mazarguil ; Olivier Matz
> Subject: Re: [dpdk-dev] [RFC] ethdev: support metadata as flow rule criteria
>
> On Wed, Aug 22, 2018 at 04:31:14PM +0300, Andrew Rybchenko wrote:
> > On 13.08.2018 10:46, Dekel Peled wrote:
> > > Current implement
On Wed, Aug 22, 2018 at 12:13:19PM +, Ananyev, Konstantin wrote:
> Hi Dekel,
>
> > >
> > >
> > > >
> > > > > -Original Message-
> > > > > From: Dekel Peled [mailto:dek...@mellanox.com]
> > > > > Sent: Monday, August 13, 2018 10:47 AM
> > > > > To: dev@dpdk.org
> > > > > Cc: Ori Kam ; S
On Wed, Aug 22, 2018 at 04:31:14PM +0300, Andrew Rybchenko wrote:
> On 13.08.2018 10:46, 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 exampl
On 8/13/2018 9:03 AM, Dekel Peled wrote:
> Adding relevant maintainers.
>
>> -Original Message-
>> From: Dekel Peled [mailto:dek...@mellanox.com]
>> Sent: Monday, August 13, 2018 10:47 AM
>> To: dev@dpdk.org
>> Cc: Ori Kam ; Shahaf Shuler
>>
>> Subject: [RFC] ethdev: support metadata as
On 13.08.2018 10:46, 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,
connected with virtio,
Hi Dekel,
> >
> >
> > >
> > > > -Original Message-
> > > > From: Dekel Peled [mailto:dek...@mellanox.com]
> > > > Sent: Monday, August 13, 2018 10:47 AM
> > > > To: dev@dpdk.org
> > > > Cc: Ori Kam ; Shahaf Shuler
> > > >
> > > > Subject: [RFC] ethdev: support metadata as flow rule criter
Thanks, PSB.
> -Original Message-
> From: Ananyev, Konstantin [mailto:konstantin.anan...@intel.com]
> Sent: Tuesday, August 21, 2018 4:08 PM
> To: Dekel Peled ; dev@dpdk.org; Adrien Mazarguil
> ; olivier.m...@6wind.com
> Cc: Ori Kam ; Shahaf Shuler
>
> Subject: RE: [RFC] ethdev: support m
>
> > -Original Message-
> > From: Dekel Peled [mailto:dek...@mellanox.com]
> > Sent: Monday, August 13, 2018 10:47 AM
> > To: dev@dpdk.org
> > Cc: Ori Kam ; Shahaf Shuler
> >
> > Subject: [RFC] ethdev: support metadata as flow rule criteria
> >
> > Current implementation of rte_flow a
Adding relevant maintainers.
> -Original Message-
> From: Dekel Peled [mailto:dek...@mellanox.com]
> Sent: Monday, August 13, 2018 10:47 AM
> To: dev@dpdk.org
> Cc: Ori Kam ; Shahaf Shuler
>
> Subject: [RFC] ethdev: support metadata as flow rule criteria
>
> Current implementation of rt
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
11 matches
Mail list logo
