From: Gaetan Rivet <gaetan.rivet@6wind.com>
To: dev@dpdk.org
Cc: Gaetan Rivet <gaetan.rivet@6wind.com>
Subject: [dpdk-dev] [PATCH 0/3] Introduce net bus
Date: Thu, 1 Jun 2017 12:44:30 +0200 [thread overview]
Message-ID: <cover.1496313294.git.gaetan.rivet@6wind.com> (raw)
This new bus takes as devices kernel netdevices.
It offers an API for drivers to register a translation layer that would
transform the netdev name to one their regular PMD would be able to
probe.
This is PoC. It currently only works for MLX4 and MLX5 PMDs as they were
bifurcated and had very little work to do otherwise.
The planned feature is for at least all PCI drivers, be able to unbind
the device from its kmod and bind it to a choosen IO module, prior to
probing.
Additional possible feature would be a close integration with eventually
NCI-like lib, to transparently capture kernel devices, keep a control
interface present and bind / unbind the underlying hardware function as
necessary.
This bus depends on plug / unplug being implemented for the sub-bus
(here, PCI or vdev). If new buses wants to be able to capture kernel
netdevices this way, they should implement plug / unplug.
This patchset depends on:
[PATCH 0/8] bus/pci: remove PCI bus from EAL
http://dpdk.org/dev/patchwork/patch/24972/
http://dpdk.org/ml/archives/dev/2017-June/067061.html
Gaetan Rivet (3):
bus/net: introduce net bus
net/mlx4: net bus support
net/mlx5: net bus support
MAINTAINERS | 6 +
config/common_linuxapp | 2 +
drivers/bus/Makefile | 2 +
drivers/bus/net/Makefile | 66 +++++++
drivers/bus/net/bsd/Makefile | 33 ++++
drivers/bus/net/include/rte_bus_net.h | 145 ++++++++++++++++
drivers/bus/net/linux/Makefile | 35 ++++
drivers/bus/net/linux/rte_bus_net.c | 237 ++++++++++++++++++++++++++
drivers/bus/net/linux/rte_bus_net_version.map | 5 +
drivers/bus/net/private.h | 143 ++++++++++++++++
drivers/bus/net/rte_bus_net.c | 210 +++++++++++++++++++++++
drivers/net/mlx4/mlx4.c | 10 ++
drivers/net/mlx5/mlx5.c | 10 ++
mk/rte.app.mk | 1 +
14 files changed, 905 insertions(+)
create mode 100644 drivers/bus/net/Makefile
create mode 100644 drivers/bus/net/bsd/Makefile
create mode 100644 drivers/bus/net/include/rte_bus_net.h
create mode 100644 drivers/bus/net/linux/Makefile
create mode 100644 drivers/bus/net/linux/rte_bus_net.c
create mode 100644 drivers/bus/net/linux/rte_bus_net_version.map
create mode 100644 drivers/bus/net/private.h
create mode 100644 drivers/bus/net/rte_bus_net.c
--
2.1.4
next reply other threads:[~2017-06-01 10:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 10:44 Gaetan Rivet [this message]
2017-06-01 10:44 ` [dpdk-dev] [PATCH 1/3] bus/net: introduce " Gaetan Rivet
2017-06-01 10:44 ` [dpdk-dev] [PATCH 2/3] net/mlx4: net bus support Gaetan Rivet
2017-06-01 10:44 ` [dpdk-dev] [PATCH 3/3] net/mlx5: " Gaetan Rivet
2017-06-08 0:00 ` [dpdk-dev] [PATCH v2 0/4] Introduce net bus Gaetan Rivet
2017-06-08 0:00 ` [dpdk-dev] [PATCH v2 1/4] bus/net: introduce " Gaetan Rivet
2017-06-08 0:00 ` [dpdk-dev] [PATCH v2 2/4] bus/net: implement hotplug bus operations Gaetan Rivet
2017-06-08 0:01 ` [dpdk-dev] [PATCH v2 3/4] net/mlx4: net bus support Gaetan Rivet
2017-06-08 0:01 ` [dpdk-dev] [PATCH v2 4/4] net/mlx5: " Gaetan Rivet
2017-06-08 7:31 ` [dpdk-dev] [PATCH v2 0/4] Introduce net bus Thomas Monjalon
2017-06-08 20:31 ` Gaëtan Rivet
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.1496313294.git.gaetan.rivet@6wind.com \
--to=gaetan.rivet@6wind.com \
--cc=dev@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 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).