From: Jan Viktorin <viktorin@rehivetech.com>
To: dev@dpdk.org
Cc: Jan Viktorin <viktorin@rehivetech.com>
Subject: [dpdk-dev] [RFC 0/6] Preview of a big eal/ethdev cleanup
Date: Mon, 18 Jan 2016 17:03:01 +0100 [thread overview]
Message-ID: <1453132987-20564-1-git-send-email-viktorin@rehivetech.com> (raw)
Hello,
based on the recent discussions [1], I have prepared a little preview of
patches reflecting the basic ideas. That is:
* generalization of device and driver structures
* embedding a generic device and driver structure in the bus-specific ones
* moving some members from PCI-specific structures to the generic ones
* introduction of the container_of macro
The code compiles for x86_64/linux/gcc, however, I didn't try any runtime yet.
[1] http://dpdk.org/ml/archives/dev/2016-January/031390.html
Regards
Jan
---
Jan Viktorin (6):
eal: introduce rte_bus_device and rte_bus_driver
eal: define macro container_of
eal: move devargs from rte_pci_device to rte_device
eal: move numa_node from rte_pci_device to rte_device
eal: move intr_handle from rte_pci_device to rte_device
eal: move driver pointer from rte_pci_device to rte_bus_device
app/test/virtual_pmd.c | 4 +--
drivers/net/e1000/em_ethdev.c | 14 +++++-----
drivers/net/e1000/igb_ethdev.c | 24 ++++++++---------
drivers/net/enic/enic_main.c | 4 +--
drivers/net/fm10k/fm10k_ethdev.c | 16 ++++++------
drivers/net/i40e/i40e_ethdev.c | 32 +++++++++++------------
drivers/net/i40e/i40e_ethdev_vf.c | 16 ++++++------
drivers/net/ixgbe/ixgbe_ethdev.c | 28 ++++++++++----------
drivers/net/virtio/virtio_ethdev.c | 41 ++++++++++++++++++------------
lib/librte_cryptodev/rte_cryptodev.c | 3 ++-
lib/librte_eal/bsdapp/eal/eal_pci.c | 16 ++++++------
lib/librte_eal/common/eal_common_pci.c | 14 +++++-----
lib/librte_eal/common/eal_common_pci_uio.c | 18 ++++++-------
lib/librte_eal/common/include/rte_common.h | 16 ++++++++++++
lib/librte_eal/common/include/rte_dev.h | 15 +++++++++++
lib/librte_eal/common/include/rte_pci.h | 10 +++++---
lib/librte_eal/linuxapp/eal/eal_pci.c | 8 +++---
lib/librte_eal/linuxapp/eal/eal_pci_uio.c | 28 ++++++++++----------
lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 14 +++++-----
lib/librte_ether/rte_ethdev.c | 16 +++++++-----
20 files changed, 191 insertions(+), 146 deletions(-)
--
2.7.0
next reply other threads:[~2016-01-18 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 16:03 Jan Viktorin [this message]
2016-01-18 16:03 ` [dpdk-dev] [RFC 1/6] eal: introduce rte_bus_device and rte_bus_driver Jan Viktorin
2016-01-18 16:03 ` [dpdk-dev] [RFC 2/6] eal: define macro container_of Jan Viktorin
2016-01-18 16:03 ` [dpdk-dev] [RFC 3/6] eal: move devargs from rte_pci_device to rte_device Jan Viktorin
2016-01-18 16:03 ` [dpdk-dev] [RFC 4/6] eal: move numa_node " Jan Viktorin
2016-01-18 16:03 ` [dpdk-dev] [RFC 5/6] eal: move intr_handle " Jan Viktorin
2016-01-18 16:03 ` [dpdk-dev] [RFC 6/6] eal: move driver pointer from rte_pci_device to rte_bus_device Jan Viktorin
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=1453132987-20564-1-git-send-email-viktorin@rehivetech.com \
--to=viktorin@rehivetech.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).