From: Bruce Richardson <bruce.richardson@intel.com>
To: nipun.gupta@nxp.com, hemant.agrawal@nxp.com
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 0/3] Minor rawdev fixes and enhancements
Date: Mon, 6 Jul 2020 11:31:29 +0100 [thread overview]
Message-ID: <20200706103132.7691-1-bruce.richardson@intel.com> (raw)
Improve the rawdev info_get function to return the numa socket id value to
the user, and to allow querying basic info of an unknown device by allowing
generic info to be returned without having to know the device type.
Also add in the missing dump function to the map file.
Bruce Richardson (3):
rawdev: allow calling info function for unknown rawdevs
rawdev: return NUMA socket id to the user
rawdev: fix missing dump function in map file
lib/librte_rawdev/rte_rawdev.c | 14 +++++++-------
lib/librte_rawdev/rte_rawdev.h | 8 +++++++-
lib/librte_rawdev/rte_rawdev_version.map | 1 +
3 files changed, 15 insertions(+), 8 deletions(-)
--
2.25.1
next reply other threads:[~2020-07-06 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 10:31 Bruce Richardson [this message]
2020-07-06 10:31 ` [dpdk-dev] [PATCH 1/3] rawdev: allow calling info function for unknown rawdevs Bruce Richardson
2020-07-07 3:40 ` Hemant Agrawal
2020-07-07 12:18 ` Thomas Monjalon
2020-07-07 12:31 ` Bruce Richardson
2020-07-06 10:31 ` [dpdk-dev] [PATCH 2/3] rawdev: return NUMA socket id to the user Bruce Richardson
2020-07-07 3:40 ` Hemant Agrawal
2020-07-07 12:23 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2020-07-07 12:33 ` Bruce Richardson
2020-07-06 10:31 ` [dpdk-dev] [PATCH 3/3] rawdev: fix missing dump function in map file Bruce Richardson
2020-07-07 3:40 ` Hemant Agrawal
2020-07-07 17:17 ` [dpdk-dev] [PATCH 0/3] Minor rawdev fixes and enhancements 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=20200706103132.7691-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=nipun.gupta@nxp.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).