Re: [PATCH 1/1] net/sfc: stop misuse of Rx ingress m-port metadata on EF100

2023-03-10 Thread Ferruh Yigit
On 3/10/2023 2:18 PM, Andrew Rybchenko wrote: > On 3/9/23 07:11, Ivan Malov wrote: >> The driver supports representor functionality. In it, >> packets coming from VFs to the dedicated back-end Rx >> queue get demultiplexed into front-end Rx queues of >> representor ethdevs as per the per-packet met

Re: [PATCH 1/1] net/sfc: stop misuse of Rx ingress m-port metadata on EF100

2023-03-10 Thread Andrew Rybchenko
On 3/9/23 07:11, Ivan Malov wrote: The driver supports representor functionality. In it, packets coming from VFs to the dedicated back-end Rx queue get demultiplexed into front-end Rx queues of representor ethdevs as per the per-packet metadata indicating logical HW ingress ports. On transmit, pa

Re: [PATCH 1/1] net/sfc: stop misuse of Rx ingress m-port metadata on EF100

2023-03-10 Thread Ferruh Yigit
On 3/9/2023 4:11 AM, Ivan Malov wrote: > The driver supports representor functionality. In it, > packets coming from VFs to the dedicated back-end Rx > queue get demultiplexed into front-end Rx queues of > representor ethdevs as per the per-packet metadata > indicating logical HW ingress ports. On

[PATCH 1/1] net/sfc: stop misuse of Rx ingress m-port metadata on EF100

2023-03-08 Thread Ivan Malov
The driver supports representor functionality. In it, packets coming from VFs to the dedicated back-end Rx queue get demultiplexed into front-end Rx queues of representor ethdevs as per the per-packet metadata indicating logical HW ingress ports. On transmit, packets are provided with symmetrical m