DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Hunt <david.hunt@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] add armv7 architecture support
Date: Fri,  2 Oct 2015 22:50:01 +0100	[thread overview]
Message-ID: <1443822602-8648-1-git-send-email-david.hunt@intel.com> (raw)

This patch provides EAL support for the ARMv7 architecture. We hope that this will encourage the ARM community to contribute PMDs for their SoCs to DPDK.

For now, we've added Intel engineers to the MAINTAINERS file. We would like to encourage the ARM community to take over maintenance of this area in future, and to further improve it.

This patch was tested on AXM5500 and Raspberry Pi 2 Model B+

Amruta Zende (1):
  lib: added support for armv7 architecture

 MAINTAINERS                                        |    5 +
 config/defconfig_arm-native-linuxapp-gcc           |   56 ++++
 .../common/include/arch/arm/rte_atomic.h           |  269 ++++++++++++++++++++
 .../common/include/arch/arm/rte_byteorder.h        |  146 +++++++++++
 .../common/include/arch/arm/rte_cpuflags.h         |  138 ++++++++++
 .../common/include/arch/arm/rte_cycles.h           |   77 ++++++
 .../common/include/arch/arm/rte_memcpy.h           |  101 ++++++++
 .../common/include/arch/arm/rte_prefetch.h         |   64 +++++
 .../common/include/arch/arm/rte_rwlock.h           |   70 +++++
 .../common/include/arch/arm/rte_spinlock.h         |  116 +++++++++
 lib/librte_eal/common/include/arch/arm/rte_vect.h  |   37 +++
 lib/librte_eal/linuxapp/Makefile                   |    3 +
 lib/librte_eal/linuxapp/arm_pmu/Makefile           |   52 ++++
 lib/librte_eal/linuxapp/arm_pmu/rte_enable_pmu.c   |   83 ++++++
 mk/arch/arm/rte.vars.mk                            |   58 +++++
 mk/machine/armv7-a/rte.vars.mk                     |   63 +++++
 mk/toolchain/gcc/rte.vars.mk                       |    8 +-
 17 files changed, 1343 insertions(+), 3 deletions(-)
 create mode 100644 config/defconfig_arm-native-linuxapp-gcc
 create mode 100644 lib/librte_eal/common/include/arch/arm/rte_atomic.h
 create mode 100644 lib/librte_eal/common/include/arch/arm/rte_byteorder.h
 create mode 100644 lib/librte_eal/common/include/arch/arm/rte_cpuflags.h
 create mode 100644 lib/librte_eal/common/include/arch/arm/rte_cycles.h
 create mode 100644 lib/librte_eal/common/include/arch/arm/rte_memcpy.h
 create mode 100644 lib/librte_eal/common/include/arch/arm/rte_prefetch.h
 create mode 100644 lib/librte_eal/common/include/arch/arm/rte_rwlock.h
 create mode 100644 lib/librte_eal/common/include/arch/arm/rte_spinlock.h
 create mode 100644 lib/librte_eal/common/include/arch/arm/rte_vect.h
 create mode 100755 lib/librte_eal/linuxapp/arm_pmu/Makefile
 create mode 100644 lib/librte_eal/linuxapp/arm_pmu/rte_enable_pmu.c
 create mode 100644 mk/arch/arm/rte.vars.mk
 create mode 100644 mk/machine/armv7-a/rte.vars.mk

-- 
1.7.4.1

             reply	other threads:[~2015-10-02 21:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 21:50 David Hunt [this message]
2015-10-02 21:50 ` [dpdk-dev] [PATCH] lib: added support for armv7 architecture David Hunt
2015-10-11 21:17   ` [dpdk-dev] " Jan Viktorin
2015-10-12 13:27     ` Hunt, David
2015-10-12 13:47       ` 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=1443822602-8648-1-git-send-email-david.hunt@intel.com \
    --to=david.hunt@intel.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).