Hi Bing, > -----Original Message----- > From: Bing Zhao <bi...@nvidia.com> > Sent: Thursday, October 8, 2020 3:05 PM > Subject: [PATCH v3 3/6] ethdev: add API to get hairpin peer ports list > > After hairpin queues are configured, in general, the application will > maintain the ports topology and even the queues configuration for > hairpin. But sometimes it will not. > > If there is no hot-plug, it is easy to bind and unbind hairpin among > all the ports. The application can just connect or disconnect the > hairpin egress ports to / from all the probed ingress ports. Then > all the connections could be handled properly. > > But with hot-plug / hot-unplug, one port could be probed and removed > dynamically. With two ports hairpin, all the connections from and to > this port should be handled after start(bind) or before stop(unbind). > It is necessary to know the hairpin topology with this port. > > This API will return the ports list with the actual peer ports number > after configuration. Either peer RX or TX ports will be gotten with > this function call. > > Signed-off-by: Bing Zhao <bi...@nvidia.com> > --- > v3: > 1. change the direction from bool to unsigned int type > 2. add length to protect the array from getting corrupted > ---
Acked-by: Ori Kam <or...@nvidia.com> Thanks, Ori
