From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: ferruh.yigit@intel.com
Cc: keith.wiles@intel.com, hemant.agrawal@nxp.com, dev@dpdk.org,
Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: [dpdk-dev] [PATCH 0/2] Adding a missing queue count API in rawdev
Date: Tue, 31 Jul 2018 16:03:01 +0530 [thread overview]
Message-ID: <20180731103303.14988-1-shreyansh.jain@nxp.com> (raw)
Recently, off the list, Keith pointed out that the rte_rawdev_queue_count
API was incomplete - only the declaration existed but no definition. This
is an old miss (and embarassingly, almost two release cycle long miss!)
This patch adds that and the relevant unit test case.
Ferruh: Though I am sending it as a fix hoping it would be possible to
merge as 'fix' for 18.08, if not, I will resend with map file changes
for early merge in 1811 window.
The changes are completely independent of any other API or driver impl.
Shreyansh Jain (2):
rawdev: fix missing queue count API
raw/skeleton: implement queue count API
drivers/raw/skeleton_rawdev/skeleton_rawdev.c | 13 ++++++++++++
.../skeleton_rawdev/skeleton_rawdev_test.c | 13 ++++++++++++
lib/librte_rawdev/rte_rawdev.c | 12 +++++++++++
lib/librte_rawdev/rte_rawdev.h | 1 +
lib/librte_rawdev/rte_rawdev_pmd.h | 20 +++++++++++++++++++
lib/librte_rawdev/rte_rawdev_version.map | 1 +
6 files changed, 60 insertions(+)
--
2.17.1
next reply other threads:[~2018-07-31 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 10:33 Shreyansh Jain [this message]
2018-07-31 10:33 ` [dpdk-dev] [PATCH 1/2] rawdev: fix missing queue count API Shreyansh Jain
2018-08-07 4:13 ` Wiles, Keith
2018-07-31 10:33 ` [dpdk-dev] [PATCH 2/2] raw/skeleton: implement " Shreyansh Jain
2018-08-07 4:15 ` Wiles, Keith
2018-08-01 16:26 ` [dpdk-dev] [PATCH 0/2] Adding a missing queue count API in rawdev Thomas Monjalon
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=20180731103303.14988-1-shreyansh.jain@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=keith.wiles@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).