From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: nipun.gupta@nxp.com, hemant.agrawal@nxp.com, dev@dpdk.org,
stable@dpdk.org, bluca@debian.org, ktraynor@redhat.com
Subject: Re: [dpdk-dev] [PATCH 1/3] rawdev: allow calling info function for unknown rawdevs
Date: Tue, 07 Jul 2020 14:18:31 +0200 [thread overview]
Message-ID: <227734353.nfkpUBtnmh@thomas> (raw)
In-Reply-To: <20200706103132.7691-2-bruce.richardson@intel.com>
06/07/2020 12:31, Bruce Richardson:
> To call the rte_rawdev_info_get() function, the user currently has to know
> the underlying type of the device in order to pass an appropriate structure
> or buffer as the dev_private pointer in the info structure. By allowing a
> NULL value for this field, we can skip getting the device-specific info and
> just return the generic info - including the device name and driver, which
> can be used to determine the device type - to the user.
>
> This ensures that basic info can be get for all rawdevs, without knowing
> the type, and even if the info driver API call has not been implemented for
> the device.
>
> Cc: stable@dpdk.org
This is a new feature. Why should it be backported?
next prev parent reply other threads:[~2020-07-07 12:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 10:31 [dpdk-dev] [PATCH 0/3] Minor rawdev fixes and enhancements Bruce Richardson
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 [this message]
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=227734353.nfkpUBtnmh@thomas \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=ktraynor@redhat.com \
--cc=nipun.gupta@nxp.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.