Re: [dpdk-dev] [PATCH v4 3/5] ethdev: add API to get hairpin peer ports list

2020-10-14 Thread Bing Zhao
beilei.x...@intel.com; > wenzhuo...@intel.com; dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v4 3/5] ethdev: add API to get > hairpin peer ports list > > External email: Use caution opening links or attachments > > > 13/10/2020 18:19, Bing Zhao: > > --- a/lib/librte_ethdev/rt

Re: [dpdk-dev] [PATCH v4 3/5] ethdev: add API to get hairpin peer ports list

2020-10-14 Thread Thomas Monjalon
13/10/2020 18:19, Bing Zhao: > --- a/lib/librte_ethdev/rte_ethdev.c > +++ b/lib/librte_ethdev/rte_ethdev.c > @@ -2208,6 +2208,30 @@ struct rte_eth_dev * > return ret; > } > > +int > +rte_eth_hairpin_get_peer_ports(uint16_t cur_port, uint16_t *peer_ports, > +size

[dpdk-dev] [PATCH v4 3/5] ethdev: add API to get hairpin peer ports list

2020-10-13 Thread Bing Zhao
After hairpin queues are configured, in general, the application will maintain the ports topology and even the queues configuration for the 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 di