DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gaetan Rivet <gaetan.rivet@6wind.com>
To: dev@dpdk.org
Cc: Gaetan Rivet <gaetan.rivet@6wind.com>,
	Jan Blunck <jblunck@infradead.org>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	David Marchand <david.marchand@6wind.com>
Subject: [dpdk-dev] [PATCH v3 0/3] eal: complete attach / detach support
Date: Thu,  8 Jun 2017 01:58:27 +0200	[thread overview]
Message-ID: <cover.1496876926.git.gaetan.rivet@6wind.com> (raw)
In-Reply-To: <cover.1496310671.git.gaetan.rivet@6wind.com>

Implements attach / detach for the PCI bus, and a streamlined attach for
the virtual bus.

This is necessary to remove the final dependencies of the EAL on the virtual
and PCI buses, due to the rte_eal_dev_attach and rte_eal_dev_detach functions.

This patchset depends on:

pci: implement find_device bus operation
http://dpdk.org/ml/archives/dev/2017-May/066340.html
http://dpdk.org/dev/patchwork/patch/24498/

[PATCH 00/14] Generic devargs parsing
http://dpdk.org/ml/archives/dev/2017-May/066351.html
http://dpdk.org/dev/patchwork/patch/24508/

v1 -> v2:

   * Rebase the series on the plug / unplug API.
   * removed the vdev_plug implementation as it is now done in
     the plug/unplug introduction.

v2 -> v3:

   * Fix a few bugs in rte_dev_attach / detach.
   * Follow new plug / unplug API.

Gaetan Rivet (3):
  pci: implement hotplug bus operation
  dev: remove vdev function dependency
  vdev: use standard bus registration function

 lib/librte_eal/common/eal_common_dev.c  | 50 ++++++++++++++----------
 lib/librte_eal/common/eal_common_pci.c  | 67 +++++++++++++++++++++++++++++++++
 lib/librte_eal/common/eal_common_vdev.c | 18 +--------
 3 files changed, 98 insertions(+), 37 deletions(-)

-- 
2.1.4

  parent reply	other threads:[~2017-06-07 23:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 15:18 [dpdk-dev] [PATCH " Gaetan Rivet
2017-05-24 15:18 ` [dpdk-dev] [PATCH 1/3] pci: implement attach/detach bus operation Gaetan Rivet
2017-05-24 15:18 ` [dpdk-dev] [PATCH 2/3] vdev: implement attach " Gaetan Rivet
2017-05-24 15:18 ` [dpdk-dev] [PATCH 3/3] vdev: use standard bus registration function Gaetan Rivet
2017-06-01 10:11 ` [dpdk-dev] [PATCH v2 0/3] eal: complete attach / detach support Gaetan Rivet
2017-06-01 10:12   ` [dpdk-dev] [PATCH v2 1/3] pci: implement plug/unplug bus operation Gaetan Rivet
2017-06-01 10:12   ` [dpdk-dev] [PATCH v2 2/3] dev: remove vdev function dependency Gaetan Rivet
2017-06-01 10:12   ` [dpdk-dev] [PATCH v2 3/3] vdev: use standard bus registration function Gaetan Rivet
2017-06-07 23:58   ` Gaetan Rivet [this message]
2017-06-07 23:58     ` [dpdk-dev] [PATCH v3 1/3] pci: implement hotplug bus operation Gaetan Rivet
2017-06-07 23:58     ` [dpdk-dev] [PATCH v3 2/3] dev: remove vdev function dependency Gaetan Rivet
2017-06-21 14:42       ` Thomas Monjalon
2017-06-07 23:58     ` [dpdk-dev] [PATCH v3 3/3] vdev: use standard bus registration function Gaetan Rivet
2017-06-21 14:41       ` 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=cover.1496876926.git.gaetan.rivet@6wind.com \
    --to=gaetan.rivet@6wind.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=jblunck@infradead.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=stephen@networkplumber.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 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).