DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Michael Baum <michaelba@nvidia.com>, <dev@dpdk.org>
Cc: Xiaoyun Li <xiaoyun.li@intel.com>,
	Aman Singh <aman.deep.singh@intel.com>,
	 Yuying Zhang <yuying.zhang@intel.com>,
	Matan Azrad <matan@nvidia.com>
Subject: Re: [PATCH 2/2] app/testpmd: add test for external RxQ
Date: Thu, 3 Mar 2022 13:02:23 +0000	[thread overview]
Message-ID: <239a6a99-1b9d-c343-e79d-6e6d67dd6901@intel.com> (raw)
In-Reply-To: <20220301202615.4103972-3-michaelba@nvidia.com>

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/ ?

And range looks odd, is [64536, 65535] correct? If so does it
deserve additional clarification?

> +* ``hw_queue_id``: queue index given by HW in queue creation.
> +
> +
>   Device Functions
>   ----------------


  reply	other threads:[~2022-03-03 13:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 20:26 [PATCH 0/2] app/testpmd: external RxQ tests Michael Baum
2022-03-01 20:26 ` [PATCH 1/2] app/testpmd: add test for remote PD and CTX Michael Baum
2022-03-03 12:57   ` Ferruh Yigit
2022-03-07 16:07     ` Michael Baum
2022-03-08  9:40       ` Thomas Monjalon
2022-03-01 20:26 ` [PATCH 2/2] app/testpmd: add test for external RxQ Michael Baum
2022-03-03 13:02   ` Ferruh Yigit [this message]
2022-03-07 15:51     ` Michael Baum
2022-06-16 17:10 ` [PATCH v2 0/2] mlx5/testpmd: external RxQ tests Michael Baum
2022-06-16 17:10   ` [PATCH v2 1/2] app/testpmd: add test for remote PD and CTX Michael Baum
2022-06-16 17:10   ` [PATCH v2 2/2] app/testpmd: add test for external RxQ Michael Baum
2022-06-21  9:27   ` [PATCH v2 0/2] mlx5/testpmd: external RxQ tests Raslan Darawsheh
2022-06-28 14:58   ` [PATCH v3 0/2] net/mlx5: " Michael Baum
2022-06-28 14:58     ` [PATCH v3 1/2] net/mlx5: add test for remote PD and CTX Michael Baum
2022-06-28 14:58     ` [PATCH v3 2/2] net/mlx5: add test for external Rx queue Michael Baum
2022-06-29  9:06     ` [PATCH v3 0/2] net/mlx5: external RxQ tests Raslan Darawsheh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=239a6a99-1b9d-c343-e79d-6e6d67dd6901@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=michaelba@nvidia.com \
    --cc=xiaoyun.li@intel.com \
    --cc=yuying.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).