From: Chao Zhu <bjzhuc@cn.ibm.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/7] Patches to split architecture specific operations from DPDK
Date: Thu, 16 Oct 2014 06:44:27 -0400 [thread overview]
Message-ID: <1413456274-22649-1-git-send-email-bjzhuc@cn.ibm.com> (raw)
The set of patches split x86 architecture specific operations from DPDK and put them to the
arch directories of i686 and x86_64 architecture. This will make the adpotion of DPDK much easier
on other computer architecture. For a new architecture, just add an architecture specific
directory and necessary building configuration files, then DPDK eal library can support it.
This is an upgrade version of the former patch.
Chao Zhu (7):
Split atomic operations to architecture specific
Split byte order operations to architecture specific
Split CPU cycle operation to architecture specific
Split prefetch operations to architecture specific
Split spinlock operations to architecture specific
Split memcpy operation to architecture specific
Split CPU flags operations to architecture specific
lib/librte_eal/common/Makefile | 21 +-
lib/librte_eal/common/eal_common_cpuflags.c | 190 ----
.../common/include/arch/i686/rte_atomic.h | 669 ++++++++++++
.../common/include/arch/i686/rte_byteorder.h | 194 ++++
.../common/include/arch/i686/rte_cpuflags.h | 364 +++++++
.../common/include/arch/i686/rte_cycles.h | 158 +++
.../common/include/arch/i686/rte_memcpy.h | 376 +++++++
.../common/include/arch/i686/rte_prefetch.h | 88 ++
.../common/include/arch/i686/rte_spinlock.h | 180 ++++
.../common/include/arch/x86_64/rte_atomic.h | 631 +++++++++++
.../common/include/arch/x86_64/rte_byteorder.h | 195 ++++
.../common/include/arch/x86_64/rte_cpuflags.h | 364 +++++++
.../common/include/arch/x86_64/rte_cycles.h | 158 +++
.../common/include/arch/x86_64/rte_memcpy.h | 376 +++++++
.../common/include/arch/x86_64/rte_prefetch.h | 88 ++
.../common/include/arch/x86_64/rte_spinlock.h | 180 ++++
lib/librte_eal/common/include/generic/rte_atomic.h | 795 ++++++++++++++
.../common/include/generic/rte_byteorder.h | 124 +++
lib/librte_eal/common/include/generic/rte_cycles.h | 190 ++++
.../common/include/generic/rte_spinlock.h | 169 +++
.../common/include/i686/arch/rte_atomic.h | 373 -------
lib/librte_eal/common/include/rte_atomic.h | 1133 --------------------
lib/librte_eal/common/include/rte_byteorder.h | 270 -----
lib/librte_eal/common/include/rte_cpuflags.h | 182 ----
lib/librte_eal/common/include/rte_cycles.h | 266 -----
lib/librte_eal/common/include/rte_memcpy.h | 376 -------
lib/librte_eal/common/include/rte_prefetch.h | 88 --
lib/librte_eal/common/include/rte_spinlock.h | 258 -----
.../common/include/x86_64/arch/rte_atomic.h | 335 ------
29 files changed, 5311 insertions(+), 3480 deletions(-)
create mode 100644 lib/librte_eal/common/include/arch/i686/rte_atomic.h
create mode 100644 lib/librte_eal/common/include/arch/i686/rte_byteorder.h
create mode 100644 lib/librte_eal/common/include/arch/i686/rte_cpuflags.h
create mode 100644 lib/librte_eal/common/include/arch/i686/rte_cycles.h
create mode 100644 lib/librte_eal/common/include/arch/i686/rte_memcpy.h
create mode 100644 lib/librte_eal/common/include/arch/i686/rte_prefetch.h
create mode 100644 lib/librte_eal/common/include/arch/i686/rte_spinlock.h
create mode 100644 lib/librte_eal/common/include/arch/x86_64/rte_atomic.h
create mode 100644 lib/librte_eal/common/include/arch/x86_64/rte_byteorder.h
create mode 100644 lib/librte_eal/common/include/arch/x86_64/rte_cpuflags.h
create mode 100644 lib/librte_eal/common/include/arch/x86_64/rte_cycles.h
create mode 100644 lib/librte_eal/common/include/arch/x86_64/rte_memcpy.h
create mode 100644 lib/librte_eal/common/include/arch/x86_64/rte_prefetch.h
create mode 100644 lib/librte_eal/common/include/arch/x86_64/rte_spinlock.h
create mode 100644 lib/librte_eal/common/include/generic/rte_atomic.h
create mode 100644 lib/librte_eal/common/include/generic/rte_byteorder.h
create mode 100644 lib/librte_eal/common/include/generic/rte_cycles.h
create mode 100644 lib/librte_eal/common/include/generic/rte_spinlock.h
delete mode 100644 lib/librte_eal/common/include/i686/arch/rte_atomic.h
delete mode 100644 lib/librte_eal/common/include/rte_atomic.h
delete mode 100644 lib/librte_eal/common/include/rte_byteorder.h
delete mode 100644 lib/librte_eal/common/include/rte_cpuflags.h
delete mode 100644 lib/librte_eal/common/include/rte_cycles.h
delete mode 100644 lib/librte_eal/common/include/rte_memcpy.h
delete mode 100644 lib/librte_eal/common/include/rte_prefetch.h
delete mode 100644 lib/librte_eal/common/include/rte_spinlock.h
delete mode 100644 lib/librte_eal/common/include/x86_64/arch/rte_atomic.h
next reply other threads:[~2014-10-16 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 10:44 Chao Zhu [this message]
2014-10-16 10:44 ` [dpdk-dev] [PATCH v2 1/7] Split atomic operations to architecture specific Chao Zhu
2014-10-16 10:44 ` [dpdk-dev] [PATCH v2 2/7] Split byte order " Chao Zhu
2014-10-16 10:44 ` [dpdk-dev] [PATCH v2 3/7] Split CPU cycle operation " Chao Zhu
2014-10-16 10:44 ` [dpdk-dev] [PATCH v2 4/7] Split prefetch operations " Chao Zhu
2014-10-16 10:44 ` [dpdk-dev] [PATCH v2 5/7] Split spinlock " Chao Zhu
2014-10-16 10:44 ` [dpdk-dev] [PATCH v2 6/7] Split memcpy operation " Chao Zhu
2014-10-16 10:44 ` [dpdk-dev] [PATCH v2 7/7] Split CPU flags operations " Chao Zhu
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=1413456274-22649-1-git-send-email-bjzhuc@cn.ibm.com \
--to=bjzhuc@cn.ibm.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).