RE: [PATCH v2 1/2] ethdev: add PHY affinity match item

Hi, > -Original Message- > From: Andrew Rybchenko > Sent: Wednesday, February 1, 2023 4:50 PM > On 1/30/23 20:00, Jiawei Wang wrote: > > For the multiple hardware ports connect to a single DPDK port > > (mhpsdp), > > Sorry, what is mhpsdp? > (m)ultiple (h)ardware (p)orts (s)ingle (D)PD

Re: [PATCH v2 1/2] ethdev: add PHY affinity match item

On 1/30/23 20:00, Jiawei Wang wrote: For the multiple hardware ports connect to a single DPDK port (mhpsdp), Sorry, what is mhpsdp? currently, there is no information to indicate the packet belongs to which hardware port. This patch introduces a new phy affinity item in rte flow API, and "

RE: [PATCH v2 1/2] ethdev: add PHY affinity match item

Hi Jiawei, > -Original Message- > From: Jiawei(Jonny) Wang > Sent: Monday, 30 January 2023 19:01 > > For the multiple hardware ports connect to a single DPDK port (mhpsdp), > currently, there is no information to indicate the packet belongs to > which hardware port. > > This patch intro

[PATCH v2 1/2] ethdev: add PHY affinity match item

For the multiple hardware ports connect to a single DPDK port (mhpsdp), currently, there is no information to indicate the packet belongs to which hardware port. This patch introduces a new phy affinity item in rte flow API, and the phy affinity value reflects the physical port of the received pac