On 2/17/2021 2:10 PM, Thomas Monjalon wrote:
17/02/2021 14:45, Ferruh Yigit:
On 7/3/2020 3:34 PM, Ferruh Yigit wrote:
On 11/19/2019 11:09 AM, Thomas Monjalon wrote:
19/11/2019 11:59, Andrew Rybchenko:
On 11/19/19 12:50 PM, Thomas Monjalon wrote:
19/11/2019 10:24, Andrew Rybchenko:
On 11/8/1
17/02/2021 14:45, Ferruh Yigit:
> On 7/3/2020 3:34 PM, Ferruh Yigit wrote:
> > On 11/19/2019 11:09 AM, Thomas Monjalon wrote:
> >> 19/11/2019 11:59, Andrew Rybchenko:
> >>> On 11/19/19 12:50 PM, Thomas Monjalon wrote:
> 19/11/2019 10:24, Andrew Rybchenko:
> > On 11/8/19 4:30 PM, Thomas Mon
On 7/3/2020 3:34 PM, Ferruh Yigit wrote:
On 11/19/2019 11:09 AM, Thomas Monjalon wrote:
19/11/2019 11:59, Andrew Rybchenko:
On 11/19/19 12:50 PM, Thomas Monjalon wrote:
19/11/2019 10:24, Andrew Rybchenko:
On 11/8/19 4:30 PM, Thomas Monjalon wrote:
08/11/2019 14:27, Andrew Rybchenko:
On 11/8
On 11/19/2019 11:09 AM, Thomas Monjalon wrote:
> 19/11/2019 11:59, Andrew Rybchenko:
>> On 11/19/19 12:50 PM, Thomas Monjalon wrote:
>>> 19/11/2019 10:24, Andrew Rybchenko:
On 11/8/19 4:30 PM, Thomas Monjalon wrote:
> 08/11/2019 14:27, Andrew Rybchenko:
>> On 11/8/19 4:17 PM, Thomas Mo
19/11/2019 11:59, Andrew Rybchenko:
> On 11/19/19 12:50 PM, Thomas Monjalon wrote:
> > 19/11/2019 10:24, Andrew Rybchenko:
> >> On 11/8/19 4:30 PM, Thomas Monjalon wrote:
> >>> 08/11/2019 14:27, Andrew Rybchenko:
> On 11/8/19 4:17 PM, Thomas Monjalon wrote:
> > 08/11/2019 13:00, Andrew Ryb
On 11/19/19 12:50 PM, Thomas Monjalon wrote:
> 19/11/2019 10:24, Andrew Rybchenko:
>> On 11/8/19 4:30 PM, Thomas Monjalon wrote:
>>> 08/11/2019 14:27, Andrew Rybchenko:
On 11/8/19 4:17 PM, Thomas Monjalon wrote:
> 08/11/2019 13:00, Andrew Rybchenko:
>> On 11/8/19 2:03 PM, Thomas Monjal
19/11/2019 10:24, Andrew Rybchenko:
> On 11/8/19 4:30 PM, Thomas Monjalon wrote:
> > 08/11/2019 14:27, Andrew Rybchenko:
> >> On 11/8/19 4:17 PM, Thomas Monjalon wrote:
> >>> 08/11/2019 13:00, Andrew Rybchenko:
> On 11/8/19 2:03 PM, Thomas Monjalon wrote:
> > 08/11/2019 11:42, Andrew Rybch
On 11/8/19 4:30 PM, Thomas Monjalon wrote:
> 08/11/2019 14:27, Andrew Rybchenko:
>> On 11/8/19 4:17 PM, Thomas Monjalon wrote:
>>> 08/11/2019 13:00, Andrew Rybchenko:
On 11/8/19 2:03 PM, Thomas Monjalon wrote:
> 08/11/2019 11:42, Andrew Rybchenko:
>> On 11/8/19 1:28 PM, Thomas Monjalon
08/11/2019 14:27, Andrew Rybchenko:
> On 11/8/19 4:17 PM, Thomas Monjalon wrote:
> > 08/11/2019 13:00, Andrew Rybchenko:
> >> On 11/8/19 2:03 PM, Thomas Monjalon wrote:
> >>> 08/11/2019 11:42, Andrew Rybchenko:
> On 11/8/19 1:28 PM, Thomas Monjalon wrote:
> > 08/11/2019 09:35, Andrew Rybch
On 11/8/19 4:17 PM, Thomas Monjalon wrote:
> 08/11/2019 13:00, Andrew Rybchenko:
>> On 11/8/19 2:03 PM, Thomas Monjalon wrote:
>>> 08/11/2019 11:42, Andrew Rybchenko:
On 11/8/19 1:28 PM, Thomas Monjalon wrote:
> 08/11/2019 09:35, Andrew Rybchenko:
>> The problem:
>>
>>
08/11/2019 14:16, Zhang, Qi Z:
> From: Ori Kam
> >
> > Yes missed somehow 6.
> > One more general comment, what happened until now? The Mark is already
> > implemented and working more then 2 years.
>
> Actually we get many complain on i40e driver does not support MARK due to
> vector path is s
08/11/2019 13:00, Andrew Rybchenko:
> On 11/8/19 2:03 PM, Thomas Monjalon wrote:
> > 08/11/2019 11:42, Andrew Rybchenko:
> >> On 11/8/19 1:28 PM, Thomas Monjalon wrote:
> >>> 08/11/2019 09:35, Andrew Rybchenko:
> The problem:
>
> PMD wants to know before port start if ap
rko
> ; Adrien Mazarguil
> ; david.march...@redhat.com;
> ktray...@redhat.com; Olivier Matz
> Subject: RE: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
> offload
>
> Yes missed somehow 6.
> One more general comment, what happened until now? The Mark is alr
> > jer...@marvell.com; Mcnamara, John ;
> > Kovacevic, Marko ; Adrien Mazarguil
> > ; david.march...@redhat.com;
> > ktray...@redhat.com; Olivier Matz
> > Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as
> > an
> > offload
>
alon
> Cc: dev@dpdk.org; pbhagavat...@marvell.com; Yigit, Ferruh
> ; jer...@marvell.com; Mcnamara, John
> ; Kovacevic, Marko
> ; Adrien Mazarguil
> ; david.march...@redhat.com;
> ktray...@redhat.com; Olivier Matz
> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type up
Mcnamara, John ;
>> Kovacevic, Marko ; Adrien Mazarguil
>> ; david.march...@redhat.com;
>> ktray...@redhat.com; Olivier Matz
>> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as
>> an offload
>>
>>
>>
>>> -Original Mes
Ori Kam ; dev@dpdk.org;
> > pbhagavat...@marvell.com; Yigit, Ferruh ;
> > jer...@marvell.com; Mcnamara, John ;
> > Kovacevic, Marko ; Adrien Mazarguil
> > ; david.march...@redhat.com;
> > ktray...@redhat.com; Olivier Matz
> > Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: ad
On 11/8/19 2:03 PM, Thomas Monjalon wrote:
> 08/11/2019 11:42, Andrew Rybchenko:
>> On 11/8/19 1:28 PM, Thomas Monjalon wrote:
>>> 08/11/2019 09:35, Andrew Rybchenko:
The problem:
PMD wants to know before port start if application wants to
to use flow MARK/FLAG in t
Marko ; Adrien Mazarguil
> ; david.march...@redhat.com;
> ktray...@redhat.com; Olivier Matz
> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
> offload
>
> 08/11/2019 11:42, Andrew Rybchenko:
> > On 11/8/19 1:28 PM, Thomas Monjalon wrote:
> > &g
08/11/2019 11:42, Andrew Rybchenko:
> On 11/8/19 1:28 PM, Thomas Monjalon wrote:
> > 08/11/2019 09:35, Andrew Rybchenko:
> >> The problem:
> >>
> >> PMD wants to know before port start if application wants to
> >> to use flow MARK/FLAG in the future. It is required because:
> >>
> >> 1
On 11/8/19 1:28 PM, Thomas Monjalon wrote:
> 08/11/2019 09:35, Andrew Rybchenko:
>> The problem:
>>
>> PMD wants to know before port start if application wants to
>> to use flow MARK/FLAG in the future. It is required because:
>>
>> 1. HW may be configured in a different way to reserve
08/11/2019 09:35, Andrew Rybchenko:
> The problem:
>
> PMD wants to know before port start if application wants to
> to use flow MARK/FLAG in the future. It is required because:
>
> 1. HW may be configured in a different way to reserve resources
>for MARK/FLAG delivery
>
> 2. Dat
: dev@dpdk.org; pbhagavat...@marvell.com; ferruh.yi...@intel.com;
jer...@marvell.com; John McNamara; Marko Kovacevic; Adrien Mazarguil;
david.march...@redhat.com; ktray...@redhat.com; Olivier Matz
Objet : Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
offload
On 11/6/1
gt; jer...@marvell.com; John McNamara ; Marko
>> Kovacevic ; Adrien Mazarguil
>> ; david.march...@redhat.com;
>> ktray...@redhat.com
>> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
>> offload
>>
>> On 11/5/19 7:37 PM, Ori Kam wro
azarguil
> ; david.march...@redhat.com;
> ktray...@redhat.com
> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
> offload
>
> On 11/5/19 7:37 PM, Ori Kam wrote:
> >
> >
> >> -Original Message-
> >> From: Andrew
t;> jer...@marvell.com; John McNamara ; Marko
>> Kovacevic ; Adrien Mazarguil
>> ; david.march...@redhat.com;
>> ktray...@redhat.com
>> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
>> offload
>>
>
> [Snip]
>
>>>
&
azarguil
> ; david.march...@redhat.com;
> ktray...@redhat.com
> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
> offload
>
[Snip]
> >
> > Yes but like I said in Mellanox PMD for example we supported the mark only
> on non-transfer flow
t;> jer...@marvell.com; John McNamara ; Marko
>> Kovacevic ; Adrien Mazarguil
>> ; david.march...@redhat.com;
>> ktray...@redhat.com
>> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
>> offload
>>
>> On 11/4/19 9:37 PM, Ori
azarguil
> ; david.march...@redhat.com;
> ktray...@redhat.com
> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
> offload
>
> On 11/4/19 9:37 PM, Ori Kam wrote:
> >> -Original Message-
> >> From: Andrew Rybchenko
> >
jer...@marvell.com; John McNamara ; Marko
>> Kovacevic ; Adrien Mazarguil
>> ; david.march...@redhat.com;
>> ktray...@redhat.com
>> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
>> offload
>>
>> On 11/3/19 1:22 PM, Ori Kam wrote:
>&
azarguil
> ; david.march...@redhat.com;
> ktray...@redhat.com
> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
> offload
>
> On 11/3/19 1:22 PM, Ori Kam wrote:
> > Hi,
> >
> >> -Original Message-
> >> From: dev O
Kovacevic
; Adrien Mazarguil
; david.march...@redhat.com;
ktray...@redhat.com
Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
offload
On 10/31/19 5:49 PM, Thomas Monjalon wrote:
31/10/2019 10:49, Andrew Rybchenko:
On 10/28/19 5:00 PM, Ori Kam wrote:
-Original Message
> ; Adrien Mazarguil
> ; david.march...@redhat.com;
> ktray...@redhat.com
> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
> offload
>
> On 10/31/19 5:49 PM, Thomas Monjalon wrote:
> > 31/10/2019 10:49, Andrew Rybchenko:
> >>
On 10/31/19 5:49 PM, Thomas Monjalon wrote:
> 31/10/2019 10:49, Andrew Rybchenko:
>> On 10/28/19 5:00 PM, Ori Kam wrote:
-Original Message-
>>> From: Andrew Rybchenko
On 10/28/19 1:50 PM, Ori Kam wrote:
> Hi Pavan,
>
> Sorry for jumping in late.
>
> I don't un
Marko ; Adrien Mazarguil
> ; david.march...@redhat.com;
> ktray...@redhat.com
> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
> offload
>
> 31/10/2019 10:49, Andrew Rybchenko:
> > On 10/28/19 5:00 PM, Ori Kam wrote:
> > >> -Origina
31/10/2019 10:49, Andrew Rybchenko:
> On 10/28/19 5:00 PM, Ori Kam wrote:
> >> -Original Message-
> > From: Andrew Rybchenko
> >> On 10/28/19 1:50 PM, Ori Kam wrote:
> >>> Hi Pavan,
> >>>
> >>> Sorry for jumping in late.
> >>>
> >>> I don't understand why we need this feature. If the user
On 10/28/19 5:00 PM, Ori Kam wrote:
Hi Andrew,
-Original Message-
From: Andrew Rybchenko
Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
offload
Hi Ori,
On 10/28/19 1:50 PM, Ori Kam wrote:
Hi Pavan,
Sorry for jumping in late.
I don't understan
Hi Andrew,
> -Original Message-
> From: Andrew Rybchenko
> Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: add flow action type update as an
> offload
>
> Hi Ori,
>
> On 10/28/19 1:50 PM, Ori Kam wrote:
> > Hi Pavan,
> >
> > Sorry for jumping in la
Hi Ori,
On 10/28/19 1:50 PM, Ori Kam wrote:
Hi Pavan,
Sorry for jumping in late.
I don't understand why we need this feature. If the user didn't set any flow
with MARK
then the user doesn't need to check it.
There is pretty long discussion on the topic already, please, read [1].
[1]
http:
Hi Pavan,
Sorry for jumping in late.
I don't understand why we need this feature. If the user didn't set any flow
with MARK
then the user doesn't need to check it.
Also it breaks compatibility.
If my understanding is correct the MARK field is going to be moved to dynamic
field, and this
wil
40 matches
Mail list logo
