On 3/3/2022 3:02 PM, Ferruh Yigit wrote: > On 3/1/2022 8:26 PM, Michael Baum wrote: > > diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst > > b/doc/guides/testpmd_app_ug/testpmd_funcs.rst > > index d6490947c4..de5665c886 100644 > > --- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst > > +++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst > > @@ -2502,6 +2502,26 @@ To cleanup txq mbufs currently cached by > driver:: > > > > If the value of ``free_cnt`` is 0, driver should free all cached mbufs. > > > > + > > +port map external RxQ > > +~~~~~~~~~~~~~~~~~~~~~ > > + > > +MLX5 internal API for external RxQ mapping management. > > + > > +Map HW queue index (32 bit) to rte_flow queue index (16 bit) for > external RxQ:: > > + > > + testpmd> port (port_id) ext_rxq map (rte_queue_id) (hw_queue_id) > > + > > +Unmap external Rx queue rte_flow index mapping:: > > + > > + testpmd> port (port_id) ext_rxq unmap (rte_queue_id) > > + > > +where: > > + > > +* ``rte_queue_id``: queue index in reage [64536, 65535]. > > s/reage/range/ ?
Yes you right, It should have been "range". Thank you for This correction. > And range looks odd, is [64536, 65535] correct? If so does it deserve > additional clarification? It is correct, it the highest 1000 numbers in 16 bits. [64536, 65535] is [UINT16_MAX - 1000 +1, UINT16_MAX]. I'll add more explanation. > > +* ``hw_queue_id``: queue index given by HW in queue creation. > > + > > + > > Device Functions > > ----------------
