DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jeff Guo <jia.guo@intel.com>
To: bernard.iremonger@intel.com, wenzhuo.lu@intel.com,
	shahafs@mellanox.com, thomas@monjalon.net, matan@mellanox.com
Cc: ferruh.yigit@intel.com, konstantin.ananyev@intel.com,
	dev@dpdk.org, jia.guo@intel.com, stephen@networkplumber.org,
	gaetan.rivet@6wind.com, qi.z.zhang@intel.com,
	arybchenko@solarflare.com, bruce.richardson@intel.com,
	shaopeng.he@intel.com, anatoly.burakov@intel.com
Subject: [dpdk-dev] [PATCH 0/3] use a common eal device event for hot-unplug
Date: Fri, 14 Dec 2018 15:45:37 +0800	[thread overview]
Message-ID: <1544773540-89825-1-git-send-email-jia.guo@intel.com> (raw)

This patch set aim to use a common eal device event mechanism to manage
devices for hot-unplug whatever device types, so the previous ethdev
remove event will be deleted and the device detach will be remove from
app into eal framework.

Jeff Guo (3):
  eal: add --dev-hotplug option
  ethdev: remove ethdev rmv interrupt
  testpmd: remove device detach into eal

 app/test-pmd/parameters.c                  |  2 --
 app/test-pmd/testpmd.c                     | 41 +++---------------------------
 drivers/bus/pci/pci_common.c               |  7 +++++
 drivers/net/failsafe/failsafe_ether.c      | 12 ++++-----
 drivers/net/failsafe/failsafe_ops.c        |  3 +--
 drivers/net/failsafe/failsafe_private.h    |  6 ++---
 drivers/net/mlx4/mlx4_intr.c               |  1 -
 drivers/net/mlx5/mlx5_ethdev.c             |  7 ++---
 lib/librte_eal/bsdapp/eal/eal.c            | 16 ++++++++++++
 lib/librte_eal/common/eal_common_options.c |  5 ++++
 lib/librte_eal/common/eal_internal_cfg.h   |  1 +
 lib/librte_eal/common/eal_options.h        |  4 ++-
 lib/librte_eal/linuxapp/eal/eal.c          | 16 ++++++++++++
 lib/librte_eal/linuxapp/eal/eal_dev.c      | 16 +++++++++++-
 lib/librte_ethdev/rte_ethdev.h             |  1 -
 15 files changed, 79 insertions(+), 59 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-12-14  7:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14  7:45 Jeff Guo [this message]
2018-12-14  7:45 ` [dpdk-dev] [PATCH 1/3] eal: add --dev-hotplug option Jeff Guo
2018-12-17 10:15   ` David Marchand
2018-12-29  4:06     ` Jeff Guo
2019-01-02 14:46       ` David Marchand
2018-12-14  7:45 ` [dpdk-dev] [PATCH 2/3] ethdev: remove ethdev rmv interrupt Jeff Guo
2018-12-14  7:45 ` [dpdk-dev] [PATCH 3/3] testpmd: remove device detach into eal Jeff Guo
2019-04-08 14:10 ` [dpdk-dev] [PATCH 0/3] use a common eal device event for hot-unplug Iremonger, Bernard
2019-04-08 14:10   ` Iremonger, Bernard
2023-06-09 17:18 ` Stephen Hemminger

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=1544773540-89825-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=konstantin.ananyev@intel.com \
    --cc=matan@mellanox.com \
    --cc=qi.z.zhang@intel.com \
    --cc=shahafs@mellanox.com \
    --cc=shaopeng.he@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=wenzhuo.lu@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).