Hi Ivan,
> -Original Message-
> From: Ivan Malov
> Subject: Re: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
>
> Hi all,
>
> I apologise for sending more mail. In fact, yet another option comes to mind.
> In
> order to move away from confusion with "port mirroring" but pr
Hi Ori, Ivan,
On 10/7/21 5:35 PM, Ivan Malov wrote:
Hi Ori,
On 07/10/2021 16:00, Ori Kam wrote:
Hi Ivan,
-Original Message-
From: Ivan Malov
Subject: Re: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
Hi all,
I apologise for sending more mail. In fact, yet another opti
Hi Ori,
On 07/10/2021 16:00, Ori Kam wrote:
Hi Ivan,
-Original Message-
From: Ivan Malov
Subject: Re: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
Hi all,
I apologise for sending more mail. In fact, yet another option comes to mind. In
order to move away from confusion
Hi all,
I apologise for sending more mail. In fact, yet another option comes to
mind. In order to move away from confusion with "port mirroring" but
preserve the "symmetry" flavour in the new name, we can go for
"SHADOW_PORT".
So, to sum up, I propose the new diagram (see the previous letter
BTW, one more alternative to "MIRROR_PORT" is "REMOTE_PORT".
On 06/10/2021 18:30, Ivan Malov wrote:
Hi Ori,
By the looks of it, we are starting to run into slight misunderstanding.
As I see it, the main consequence of our Sep 14 gathering in Jitsi was
understanding of the fact that the concept
Hi Ori,
By the looks of it, we are starting to run into slight misunderstanding.
As I see it, the main consequence of our Sep 14 gathering in Jitsi was
understanding of the fact that the concept of item / action PORT_ID is
vague and needs a replacement. As a bare minimum, separate items
should b
Hi Ori, Andrew,
On 05/10/2021 12:19, Andrew Rybchenko wrote:
Hi Ori,
On 10/5/21 9:20 AM, Ori Kam wrote:
Hi Ivan,
-Original Message-
From: Ivan Malov
Cc: dev@dpdk.org
Subject: Re: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
Hi Ori,
On 04/10/2021 14:37, Ori Kam wrote:
Hi Ivan,
> -Original Message-
> From: Ivan Malov
> Cc: dev@dpdk.org
> Subject: Re: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
>
> Hi Ori,
>
> On 04/10/2021 14:37, Ori Kam wrote:
> > Hi Ivan,
> >
> >> -Original Message-
> >> From: Ivan Malov
> >> Sent: Monday, Oc
Hi Ori,
On 10/5/21 9:20 AM, Ori Kam wrote:
> Hi Ivan,
>
>> -Original Message-
>> From: Ivan Malov
>> Cc: dev@dpdk.org
>> Subject: Re: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
>>
>> Hi Ori,
>>
>> On 04/10/2021 14:37, Ori Kam wrote:
>>> Hi Ivan,
>>>
-Original Mes
Hi Ivan,
> -Original Message-
> From: Ivan Malov
> Sent: Monday, October 4, 2021 2:06 PM
> Cc: dev@dpdk.org
> Subject: Re: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
>
> Hi Ori,
>
> On 04/10/2021 08:45, Ori Kam wrote:
> > Hi Ivan,
> >
> >> -Original Message-
> >>
Hi Ori,
On 04/10/2021 14:37, Ori Kam wrote:
Hi Ivan,
-Original Message-
From: Ivan Malov
Sent: Monday, October 4, 2021 2:06 PM
Cc: dev@dpdk.org
Subject: Re: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
Hi Ori,
On 04/10/2021 08:45, Ori Kam wrote:
Hi Ivan,
-Origin
Hi Ori,
On 04/10/2021 08:45, Ori Kam wrote:
Hi Ivan,
-Original Message-
From: Ivan Malov
Sent: Sunday, October 3, 2021 9:11 PM
Subject: Re: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
On 03/10/2021 15:40, Ori Kam wrote:
Hi Andrew and Ivan,
-Original Message---
Hi Ivan,
> -Original Message-
> From: Ivan Malov
> Sent: Sunday, October 3, 2021 9:11 PM
> Subject: Re: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
>
>
>
> On 03/10/2021 15:40, Ori Kam wrote:
> > Hi Andrew and Ivan,
> >
> >> -Original Message-
> >> From: Andrew R
On 03/10/2021 15:40, Ori Kam wrote:
Hi Andrew and Ivan,
-Original Message-
From: Andrew Rybchenko
Sent: Friday, October 1, 2021 4:47 PM
Subject: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
From: Ivan Malov
For use with "transfer" flows. Supposed to match traffic en
Hi Andrew and Ivan,
> -Original Message-
> From: Andrew Rybchenko
> Sent: Friday, October 1, 2021 4:47 PM
> Subject: [PATCH v1 02/12] ethdev: add eswitch port item to flow API
>
> From: Ivan Malov
>
> For use with "transfer" flows. Supposed to match traffic entering the e-switch
> from
From: Ivan Malov
For use with "transfer" flows. Supposed to match traffic entering
the e-switch from the external world (network, guests) via the
port which is logically connected with the given ethdev.
Must not be combined with attributes "ingress" / "egress".
This item is meant to use the sam
16 matches
Mail list logo
