On 2/2/23 14:29, Thomas Monjalon wrote:
02/02/2023 10:21, Andrew Rybchenko:
On 2/1/23 16:48, Thomas Monjalon wrote:
01/02/2023 12:38, Andrew Rybchenko:
On 2/1/23 14:18, Thomas Monjalon wrote:
01/02/2023 12:10, Andrew Rybchenko:
On 2/1/23 13:58, Thomas Monjalon wrote:
01/02/2023 11:17, Andre
02/02/2023 10:21, Andrew Rybchenko:
> On 2/1/23 16:48, Thomas Monjalon wrote:
> > 01/02/2023 12:38, Andrew Rybchenko:
> >> On 2/1/23 14:18, Thomas Monjalon wrote:
> >>> 01/02/2023 12:10, Andrew Rybchenko:
> On 2/1/23 13:58, Thomas Monjalon wrote:
> > 01/02/2023 11:17, Andrew Rybchenko:
> >
On 2/1/23 16:48, Thomas Monjalon wrote:
01/02/2023 12:38, Andrew Rybchenko:
On 2/1/23 14:18, Thomas Monjalon wrote:
01/02/2023 12:10, Andrew Rybchenko:
On 2/1/23 13:58, Thomas Monjalon wrote:
01/02/2023 11:17, Andrew Rybchenko:
On 1/18/23 19:18, Thomas Monjalon wrote:
18/01/2023 08:28, Andr
Hi Ivan,
> -Original Message-
> From: Ivan Malov
> Sent: Wednesday, 1 February 2023 16:04
>
> On Wed, 1 Feb 2023, Thomas Monjalon wrote:
>
> > 01/02/2023 12:50, Ivan Malov:
> >> On Wed, 1 Feb 2023, Thomas Monjalon wrote:
> >>> 31/01/2023 06:30, Ivan Malov:
> I still hope community
01/02/2023 15:04, Ivan Malov:
> On Wed, 1 Feb 2023, Thomas Monjalon wrote:
> > The template flow API is experimental and will probably remain as such
> > for a long time, so if you find a more elegant approach,
> > we will consider it.
>
> Thanks for explaining this.
>
> You know, now you mention
On Wed, 1 Feb 2023, Thomas Monjalon wrote:
01/02/2023 12:50, Ivan Malov:
On Wed, 1 Feb 2023, Thomas Monjalon wrote:
31/01/2023 06:30, Ivan Malov:
I still hope community will comment on the possibility to
provide a hint mechanism for always-the-same match items,
with the perspective of becomin
01/02/2023 12:38, Andrew Rybchenko:
> On 2/1/23 14:18, Thomas Monjalon wrote:
> > 01/02/2023 12:10, Andrew Rybchenko:
> >> On 2/1/23 13:58, Thomas Monjalon wrote:
> >>> 01/02/2023 11:17, Andrew Rybchenko:
> On 1/18/23 19:18, Thomas Monjalon wrote:
> > 18/01/2023 08:28, Andrew Rybchenko:
>
01/02/2023 12:50, Ivan Malov:
> On Wed, 1 Feb 2023, Thomas Monjalon wrote:
> > 31/01/2023 06:30, Ivan Malov:
> >> I still hope community will comment on the possibility to
> >> provide a hint mechanism for always-the-same match items,
> >> with the perspective of becoming more versatile.
> >
> > An
Hi Thomas,
On Wed, 1 Feb 2023, Thomas Monjalon wrote:
31/01/2023 06:30, Ivan Malov:
Hi Rongwei,
OK, I hear ya. Thanks for persevering.
I still hope community will comment on the possibility to
provide a hint mechanism for always-the-same match items,
with the perspective of becoming more ver
On 2/1/23 14:18, Thomas Monjalon wrote:
01/02/2023 12:10, Andrew Rybchenko:
On 2/1/23 13:58, Thomas Monjalon wrote:
01/02/2023 11:17, Andrew Rybchenko:
On 1/18/23 19:18, Thomas Monjalon wrote:
18/01/2023 08:28, Andrew Rybchenko:
On 11/14/22 14:59, Rongwei Liu wrote:
In case flow rules match
On 2/1/23 14:22, Ori Kam wrote:
Hi
Please also see my previous mail.
-Original Message-
From: Andrew Rybchenko
Sent: Wednesday, 1 February 2023 13:11
On 2/1/23 13:58, Thomas Monjalon wrote:
01/02/2023 11:17, Andrew Rybchenko:
On 1/18/23 19:18, Thomas Monjalon wrote:
18/01/2023 08:
Hi
Please also see my previous mail.
> -Original Message-
> From: Andrew Rybchenko
> Sent: Wednesday, 1 February 2023 13:11
>
> On 2/1/23 13:58, Thomas Monjalon wrote:
> > 01/02/2023 11:17, Andrew Rybchenko:
> >> On 1/18/23 19:18, Thomas Monjalon wrote:
> >>> 18/01/2023 08:28, Andrew Ry
01/02/2023 12:12, Ori Kam:
> 1. we don't have at this point a way in the rte_flow template tables a way to
> set a fix match.
> Meaning to say all rules should match ip src = x
> When we create a template we are just saying on which fields/items we want to
> match
> not the value.
> So if ip src
01/02/2023 12:10, Andrew Rybchenko:
> On 2/1/23 13:58, Thomas Monjalon wrote:
> > 01/02/2023 11:17, Andrew Rybchenko:
> >> On 1/18/23 19:18, Thomas Monjalon wrote:
> >>> 18/01/2023 08:28, Andrew Rybchenko:
> On 11/14/22 14:59, Rongwei Liu wrote:
> > In case flow rules match only one kind o
Hi
> -Original Message-
> From: Thomas Monjalon
> Sent: Wednesday, 1 February 2023 12:59
>
> 01/02/2023 11:17, Andrew Rybchenko:
> > On 1/18/23 19:18, Thomas Monjalon wrote:
> > > 18/01/2023 08:28, Andrew Rybchenko:
> > >> On 11/14/22 14:59, Rongwei Liu wrote:
> > >>> In case flow rules
On 2/1/23 13:58, Thomas Monjalon wrote:
01/02/2023 11:17, Andrew Rybchenko:
On 1/18/23 19:18, Thomas Monjalon wrote:
18/01/2023 08:28, Andrew Rybchenko:
On 11/14/22 14:59, Rongwei Liu wrote:
In case flow rules match only one kind of traffic in a flow table,
then optimization can be done via a
01/02/2023 11:17, Andrew Rybchenko:
> On 1/18/23 19:18, Thomas Monjalon wrote:
> > 18/01/2023 08:28, Andrew Rybchenko:
> >> On 11/14/22 14:59, Rongwei Liu wrote:
> >>> In case flow rules match only one kind of traffic in a flow table,
> >>> then optimization can be done via allocation of this table
On 1/18/23 19:18, Thomas Monjalon wrote:
18/01/2023 08:28, Andrew Rybchenko:
On 11/14/22 14:59, Rongwei Liu wrote:
In case flow rules match only one kind of traffic in a flow table,
then optimization can be done via allocation of this table.
Such optimization is possible only if the application
31/01/2023 06:30, Ivan Malov:
> Hi Rongwei,
>
> OK, I hear ya. Thanks for persevering.
>
> I still hope community will comment on the possibility to
> provide a hint mechanism for always-the-same match items,
> with the perspective of becoming more versatile.
Any hint could be imagined.
But plea
; Andrew Rybchenko
> ; dev@dpdk.org; Raslan Darawsheh
>
> Subject: RE: [PATCH v7] ethdev: add special flags when creating async transfer
> table
>
> External email: Use caution opening links or attachments
>
>
> Hi Rongwei,
>
> OK, I hear ya. Thanks for
h
; Yuying Zhang ;
Ferruh Yigit ; Andrew Rybchenko
; dev@dpdk.org; Raslan Darawsheh
Subject: RE: [PATCH v7] ethdev: add special flags when creating async transfer
table
External email: Use caution opening links or attachments
Hi Rongwei,
Thanks for the professional attitude.
Hope this discussion
; Andrew Rybchenko
> ; dev@dpdk.org; Raslan Darawsheh
>
> Subject: RE: [PATCH v7] ethdev: add special flags when creating async transfer
> table
>
> External email: Use caution opening links or attachments
>
>
> Hi Rongwei,
>
> Thanks for the professional attitud
; Slava Ovsiienko
; Ori Kam ; NBU-Contact-
Thomas Monjalon (EXTERNAL) ; Aman Singh
; Yuying Zhang ;
Ferruh Yigit ; Andrew Rybchenko
; dev@dpdk.org; Raslan Darawsheh
Subject: RE: [PATCH v7] ethdev: add special flags when creating async transfer
table
External email: Use caution opening links or
; Andrew Rybchenko
> ; dev@dpdk.org; Raslan Darawsheh
>
> Subject: RE: [PATCH v7] ethdev: add special flags when creating async transfer
> table
>
> External email: Use caution opening links or attachments
>
>
> Hi Rongwei,
>
> For my responses, PSB.
>
> By
:00
To: Rongwei Liu
Cc: Matan Azrad ; Slava Ovsiienko
; Ori Kam ; NBU-Contact-
Thomas Monjalon (EXTERNAL) ; Aman Singh
; Yuying Zhang ;
Ferruh Yigit ; Andrew Rybchenko
; dev@dpdk.org; Raslan Darawsheh
Subject: Re: [PATCH v7] ethdev: add special flags when creating async transfer
table
External email
; Andrew Rybchenko
> ; dev@dpdk.org; Raslan Darawsheh
>
> Subject: Re: [PATCH v7] ethdev: add special flags when creating async transfer
> table
>
> External email: Use caution opening links or attachments
>
>
> Hi Rongwei,
>
> Thanks for persevering. I have no str
Hi Rongwei,
Thanks for persevering. I have no strong opinion, but, at least, the
fact that the new flags are no longer meant for use in rte_flow_attr,
which is clearly not the right place for such, is an improvement.
However, let's take a closer look at the current patch, shall we?
But, before
18/01/2023 08:28, Andrew Rybchenko:
> On 11/14/22 14:59, Rongwei Liu wrote:
> > In case flow rules match only one kind of traffic in a flow table,
> > then optimization can be done via allocation of this table.
> > Such optimization is possible only if the application gives a hint
> > about its usa
On 1/17/23 18:13, Ferruh Yigit wrote:
On 11/14/2022 11:59 AM, Rongwei Liu wrote:
In case flow rules match only one kind of traffic in a flow table,
then optimization can be done via allocation of this table.
Such optimization is possible only if the application gives a hint
about its usage of th
On 11/14/22 14:59, Rongwei Liu wrote:
In case flow rules match only one kind of traffic in a flow table,
then optimization can be done via allocation of this table.
Such optimization is possible only if the application gives a hint
about its usage of the table during initial configuration.
The t
jalon (EXTERNAL)
> Cc: dev@dpdk.org; Raslan Darawsheh
> Subject: Re: [PATCH v7] ethdev: add special flags when creating async transfer
> table
>
> External email: Use caution opening links or attachments
>
>
> On 1/17/2023 3:13 PM, Ferruh Yigit wrote:
> > On 11/14/
On 1/17/2023 3:13 PM, Ferruh Yigit wrote:
> On 11/14/2022 11:59 AM, Rongwei Liu wrote:
>> In case flow rules match only one kind of traffic in a flow table,
>> then optimization can be done via allocation of this table.
>> Such optimization is possible only if the application gives a hint
>> about
On 11/14/2022 11:59 AM, Rongwei Liu wrote:
> In case flow rules match only one kind of traffic in a flow table,
> then optimization can be done via allocation of this table.
> Such optimization is possible only if the application gives a hint
> about its usage of the table during initial configurat
In case flow rules match only one kind of traffic in a flow table,
then optimization can be done via allocation of this table.
Such optimization is possible only if the application gives a hint
about its usage of the table during initial configuration.
The transfer domain rules may process traffic
34 matches
Mail list logo
