From: Alexander Kozyrev <akozyrev@nvidia.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [RFC] net/mlx5: Descriptor status for Vectorized and MPRQ Rx
Date: Wed, 26 Aug 2020 21:16:29 +0000 [thread overview]
Message-ID: <BN7PR12MB2707E00A698C33BFA4E3E960AF540@BN7PR12MB2707.namprd12.prod.outlook.com> (raw)
There are two APIs that allow getting more insights about Rx queue operations:
- the rte_eth_rx_queue_count API gives the number of used descriptors.
- the rte_eth_rx_descriptor_status API provides the status of a Rx descriptor.
This information is available only for the regular Rx burst in the mlx5 driver.
The ENOTSUP value is returned for the Vectorized Rx burst or the MPRQ Rx burst.
Need to implement corresponding functions to compute the number of used
descriptors in an Rx queue for every Rx burst version available to DPDK users.
Once this is done we can check the required descriptor and tell whether it is
available for the hardware or being processed by the driver software.
Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
reply other threads:[~2020-08-26 21:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BN7PR12MB2707E00A698C33BFA4E3E960AF540@BN7PR12MB2707.namprd12.prod.outlook.com \
--to=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
/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).