Hi Bing, > -----Original Message----- > From: Bing Zhao <bi...@nvidia.com> > Sent: Thursday, October 8, 2020 11:52 AM > Subject: [PATCH v2 4/6] ethdev: add APIs for hairpin queue operation > > Every hairpin queue pair should be configured properly and the > connection between TX and RX queues should be established, before > hairpin function works. In single port hairpin mode, the queues of > each pair belong to the same device. It is easy to get the hardware > and software information of each queue and configure the hairpin > connection with such information. In two ports hairpin mode, it is > not easy or inappropriate to access one queue's information from > another device. > > Since hairpin is configured per queue pair, three new APIs are > introduced and they are internal for the PMD using. > > The peer update API helps to pass one queue's information to the > peer queue and get the peer's information back for the next step. > The peer bind API configures the current queue with the peer's > information. For each hairpin queue pair, this API may need to be > called twice to configure the TX, RX queues separately. > The peer unbind API resets the current queue configuration and state > to disconnect it from the peer queue. Also, it may need to be called > twice to disconnect TX, RX queues from each other. > > Some parameter of the above APIs might not be mandatory, and it > depends on the PMD implementation. > > The structure of `rte_hairpin_peer_info` is only a declaration and > the actual members will be defined in each PMD when being used. > > Signed-off-by: Bing Zhao <bi...@nvidia.com> > ---
Acked-by: Ori Kam <or...@nvidia.com> Thanks, Ori
