From: "Hunt, David" <david.hunt@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 00/12] DPDK armv8-a support
Date: Tue, 3 Nov 2015 14:17:38 +0000 [thread overview]
Message-ID: <5638C202.1050205@intel.com> (raw)
In-Reply-To: <1446556153-18845-1-git-send-email-jerin.jacob@caviumnetworks.com>
On 03/11/2015 13:09, Jerin Jacob wrote:
> This is the v1 patchset for ARMv8 that now sits on top of the v6 patch
> of the ARMv7 code by RehiveTech. It adds code into the same arm include
> directory, reducing code duplication.
>
> Tested on an ThunderX arm 64-bit arm server board, with PCI slots. Passes traffic
> between two physical ports on an Intel 82599 dual-port 10Gig NIC. Should
> work with many other NICS as long as long as there is no unaligned access to
> device memory but not yet untested.
I have your patchset building and running on an X-Gene based 8-core
MP30AR0 system, passing traffic between two ports on and 82599 also.
> Notes on arm64 kernel configuration:
>
> Tested on using Ubuntu 14.04 LTS with a 3.18 kernel and igb_uio.
> ARM64 kernels does not have functional resource mapping of PCI memory
> (PCI_MMAP), so the pci driver needs to be patched to enable this. The
> symptom of this is when /sys/bus/pci/devices/0000:0X:00.Y directory is
> missing the resource0...N files for mmapping the device memory.
>
> Following patch fixes the PCI resource mapping issue om armv8.
> Its not yet up streamed.We are in the process of up streaming it.
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/358906.html
Good to see that there's a patch on the way for this. That fix looks
almost exactly the same as the hack I did to my kernel :)
I had a couple of small issues when patching/building:
1. Three of the files had an extra blank line at the end. Maybe worth
running checkpatch on the patches. 'git am' was complaining.
2. I had problems compiling two drivers because they were attempting to
include tmmintrin.h:
...dpdk/drivers/net/fm10k/fm10k_rxtx_vec.c:41:23: fatal error:
tmmintrin.h: No such file or directory
...dpdk/drivers/net/i40e/i40e_rxtx_vec.c:43:23: fatal error:
tmmintrin.h: No such file or directory
To avoid this, I added the following two lines into
defconfig_arm64-armv8a-linuxapp-gcc
CONFIG_RTE_LIBRTE_FM10K_PMD=n
CONFIG_RTE_LIBRTE_I40E_PMD=n
and then it built fine, and I can run testpmd with my 82599's and run
autotests.
Thanks for that.
Dave.
next prev parent reply other threads:[~2015-11-03 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 13:09 Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 01/12] eal: arm64: add armv8-a version of rte_atomic_64.h Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 02/12] eal: arm64: add armv8-a version of rte_cpuflags_64.h Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 03/12] eal: arm64: add armv8-a version of rte_prefetch_64.h Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 04/12] eal: arm64: add armv8-a version of rte_cycles_64.h Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 05/12] eal: arm64: rte_memcpy_64.h version based libc memcpy Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 06/12] eal: arm: ret_vector.h improvements Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 07/12] app: test: added the new cpu flags of arm64 in test_cpuflags test case Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 08/12] acl: arm64: acl implementation using NEON gcc intrinsic Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 09/12] mk: add support for armv8 on top of armv7 Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 10/12] mk: add support for thunderx machine target based armv8-a Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 11/12] updated release note for armv8 support for DPDK 2.2 Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 12/12] maintainers: claim responsibility for ARMv8 Jerin Jacob
2015-11-03 14:17 ` Hunt, David [this message]
2015-11-03 16:38 ` [dpdk-dev] [PATCH 00/12] DPDK armv8-a support Jerin Jacob
2015-11-05 14:39 ` Hunt, David
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=5638C202.1050205@intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
/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).