Re: [PATCH v4] ethdev: add special flags when creating async transfer table

09/11/2022 10:36, Andrew Rybchenko: > On 11/9/22 12:03, Thomas Monjalon wrote: > > 09/11/2022 09:53, Andrew Rybchenko: > >> On 11/8/22 18:25, Thomas Monjalon wrote: > >>> 08/11/2022 15:38, Andrew Rybchenko: > On 11/8/22 16:29, Thomas Monjalon wrote: > > 08/11/2022 12:47, Andrew Rybchenko:

Re: [PATCH v4] ethdev: add special flags when creating async transfer table

On 11/9/22 12:03, Thomas Monjalon wrote: 09/11/2022 09:53, Andrew Rybchenko: On 11/8/22 18:25, Thomas Monjalon wrote: 08/11/2022 15:38, Andrew Rybchenko: On 11/8/22 16:29, Thomas Monjalon wrote: 08/11/2022 12:47, Andrew Rybchenko: On 11/8/22 14:39, Andrew Rybchenko wrote: On 11/4/22 13:44,

Re: [PATCH v4] ethdev: add special flags when creating async transfer table

09/11/2022 09:53, Andrew Rybchenko: > On 11/8/22 18:25, Thomas Monjalon wrote: > > 08/11/2022 15:38, Andrew Rybchenko: > >> On 11/8/22 16:29, Thomas Monjalon wrote: > >>> 08/11/2022 12:47, Andrew Rybchenko: > On 11/8/22 14:39, Andrew Rybchenko wrote: > > On 11/4/22 13:44, Rongwei Liu wrote

Re: [PATCH v4] ethdev: add special flags when creating async transfer table

On 11/8/22 18:25, Thomas Monjalon wrote: 08/11/2022 15:38, Andrew Rybchenko: On 11/8/22 16:29, Thomas Monjalon wrote: 08/11/2022 12:47, Andrew Rybchenko: On 11/8/22 14:39, Andrew Rybchenko wrote: On 11/4/22 13:44, Rongwei Liu wrote: diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h

Re: [PATCH v4] ethdev: add special flags when creating async transfer table

08/11/2022 15:38, Andrew Rybchenko: > On 11/8/22 16:29, Thomas Monjalon wrote: > > 08/11/2022 12:47, Andrew Rybchenko: > >> On 11/8/22 14:39, Andrew Rybchenko wrote: > >>> On 11/4/22 13:44, Rongwei Liu wrote: > diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h > index 8858b56428.

Re: [PATCH v4] ethdev: add special flags when creating async transfer table

On 11/8/22 16:29, Thomas Monjalon wrote: 08/11/2022 12:47, Andrew Rybchenko: On 11/8/22 14:39, Andrew Rybchenko wrote: On 11/4/22 13:44, Rongwei Liu wrote: diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h index 8858b56428..1eab12796f 100644 --- a/lib/ethdev/rte_flow.h +++ b/lib/ethde

Re: [PATCH v4] ethdev: add special flags when creating async transfer table

08/11/2022 12:47, Andrew Rybchenko: > On 11/8/22 14:39, Andrew Rybchenko wrote: > > On 11/4/22 13:44, Rongwei Liu wrote: > >> diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h > >> index 8858b56428..1eab12796f 100644 > >> --- a/lib/ethdev/rte_flow.h > >> +++ b/lib/ethdev/rte_flow.h > >> @@

Re: [PATCH v4] ethdev: add special flags when creating async transfer table

On 11/8/22 14:39, Andrew Rybchenko wrote: On 11/4/22 13:44, Rongwei Liu wrote: diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h index 8858b56428..1eab12796f 100644 --- a/lib/ethdev/rte_flow.h +++ b/lib/ethdev/rte_flow.h @@ -5186,6 +5186,34 @@ rte_flow_actions_template_destroy(uint16_t

Re: [PATCH v4] ethdev: add special flags when creating async transfer table

On 11/4/22 13:44, Rongwei Liu wrote: The transfer domain rule is able to match traffic wire/vport origin which are corresponding to two kinds of underlayer resources. Wire means traffic arrives from the uplink port while vport means traffic initiated from VF/SF. In customer deployments, they us

[PATCH v4] ethdev: add special flags when creating async transfer table

The transfer domain rule is able to match traffic wire/vport origin which are corresponding to two kinds of underlayer resources. Wire means traffic arrives from the uplink port while vport means traffic initiated from VF/SF. In customer deployments, they usually match only one kind of traffic in

[PATCH v4] ethdev: add special flags when creating async transfer table

The transfer domain rule is able to match traffic wire/vport origin which are corresponding to two kinds of underlayer resources. Wire means traffic arrives from the uplink port while vport means traffic initiated from VF/SF. In customer deployments, they usually match only one kind of traffic in