From: Stephen Hemminger <stephen@networkplumber.org>
To: Jeff Guo <jia.guo@intel.com>
Cc: ferruh.yigit@intel.com, konstantin.ananyev@intel.com,
anatoly.burakov@intel.com, thomas@monjalon.net,
bernard.iremonger@intel.com, dev@dpdk.org, helin.zhang@intel.com,
gaetan.rivet@6wind.com, qi.z.zhang@intel.com,
arybchenko@solarflare.com, bruce.richardson@intel.com,
matan@mellanox.com, shaopeng.he@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] eal: expose device states in rte device
Date: Wed, 7 Nov 2018 11:32:29 -0800 [thread overview]
Message-ID: <20181107113229.664d0696@shemminger-XPS-13-9360> (raw)
In-Reply-To: <1541583691-145432-2-git-send-email-jia.guo@intel.com>
On Wed, 7 Nov 2018 17:41:30 +0800
Jeff Guo <jia.guo@intel.com> wrote:
> Since the hotplug API and device event API have make public, so in order
> to let applications or driver deal with device directly, it would be
> helpful if the states of device could be exposed, especially for hotplug
> process.
>
> This patch will add some devices states in rte device structure
> to recode the device's current status, such as “RTE_DEV_UNUSED”,
> “RTE_DEV_ATTACHED” and “RTE_DEV_REMOVED”.
>
> Signed-off-by: Jeff Guo <jia.guo@intel.com>
Looks good.
I did spot a couple of minor nits you might want to address if
resending this.
> ---
> lib/librte_eal/common/include/rte_dev.h | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/lib/librte_eal/common/include/rte_dev.h b/lib/librte_eal/common/include/rte_dev.h
> index cd6c187..1bab0dd 100644
> --- a/lib/librte_eal/common/include/rte_dev.h
> +++ b/lib/librte_eal/common/include/rte_dev.h
> @@ -151,6 +151,18 @@ struct rte_driver {
> #define RTE_DEV_NAME_MAX_LEN 64
>
> /**
> + * Possible states of an rte devcie.
> + */
s/devcie/device/
> +enum rte_dev_state {
> + /** Device is unused before being hotplug add. */
> + RTE_DEV_UNUSED = 0,
> + /** Device is attached when allocated in probing. */
> + RTE_DEV_ATTACHED,
> + /** Device is in removed state when plug-out is detected. */
> + RTE_DEV_REMOVED,
> +};
> +
> +/**
> * A structure describing a generic device.
> */
> struct rte_device {
> @@ -160,6 +172,7 @@ struct rte_device {
> const struct rte_bus *bus; /**< Bus handle assigned on scan */
> int numa_node; /**< NUMA node connection */
> struct rte_devargs *devargs; /**< Arguments for latest probing */
> + enum rte_dev_state state; /**< Flag indicating the device state */
Why not align comment with other fields here?
> };
>
> /**
next prev parent reply other threads:[~2018-11-07 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 9:41 [dpdk-dev] [PATCH 0/2] expose device states for hot-unplug Jeff Guo
2018-11-07 9:41 ` [dpdk-dev] [PATCH 1/2] eal: expose device states in rte device Jeff Guo
2018-11-07 19:32 ` Stephen Hemminger [this message]
2018-11-09 7:35 ` Jeff Guo
2018-11-07 9:41 ` [dpdk-dev] [PATCH 2/2] but/pci: fix fd close for hot-unplug Jeff Guo
2018-11-07 19:33 ` Stephen Hemminger
2018-11-08 3:10 ` Jeff Guo
2018-11-08 21:55 ` Stephen Hemminger
2018-11-09 3:26 ` Jeff Guo
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=20181107113229.664d0696@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=arybchenko@solarflare.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gaetan.rivet@6wind.com \
--cc=helin.zhang@intel.com \
--cc=jia.guo@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=matan@mellanox.com \
--cc=qi.z.zhang@intel.com \
--cc=shaopeng.he@intel.com \
--cc=thomas@monjalon.net \
/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).