DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jeff Guo <jia.guo@intel.com>
To: ferruh.yigit@intel.com, konstantin.ananyev@intel.com,
	anatoly.burakov@intel.com, thomas@monjalon.net,
	bernard.iremonger@intel.com
Cc: dev@dpdk.org, jia.guo@intel.com, helin.zhang@intel.com,
	stephen@networkplumber.org, gaetan.rivet@6wind.com,
	qi.z.zhang@intel.com, arybchenko@solarflare.com,
	bruce.richardson@intel.com, matan@mellanox.com,
	shaopeng.he@intel.com
Subject: [dpdk-dev] [PATCH 0/2] expose device states for hot-unplug
Date: Wed,  7 Nov 2018 17:41:29 +0800	[thread overview]
Message-ID: <1541583691-145432-1-git-send-email-jia.guo@intel.com> (raw)

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, when device is hot-unplugged, some invalid process should be
skipped by checking the device status. It will avoid some error occur and
unnecessary loading.

So it is proposed that let eal framework take the control of device, it
provide device control APIs and device status checking. Something like
the rte_eth_dev_state for ethernet device could be delete later if it is
no specific usage and could be covered by the common rte device state.

Jeff Guo (2):
  eal: expose device states in rte device
  but/pci: fix fd close for hot-unplug

 drivers/bus/pci/linux/pci_uio.c         |  3 +++
 drivers/bus/pci/pci_common_uio.c        | 16 +++++++++-------
 lib/librte_eal/common/include/rte_dev.h | 13 +++++++++++++
 lib/librte_eal/linuxapp/eal/eal_dev.c   |  1 +
 4 files changed, 26 insertions(+), 7 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-11-07  9:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07  9:41 Jeff Guo [this message]
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
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=1541583691-145432-1-git-send-email-jia.guo@intel.com \
    --to=jia.guo@intel.com \
    --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=konstantin.ananyev@intel.com \
    --cc=matan@mellanox.com \
    --cc=qi.z.zhang@intel.com \
    --cc=shaopeng.he@intel.com \
    --cc=stephen@networkplumber.org \
    --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).