From: "Hunt, David" <david.hunt@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Jan Viktorin <viktorin@rehivetech.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6 00/15] Support ARMv7 architecture
Date: Tue, 3 Nov 2015 11:33:18 +0000 [thread overview]
Message-ID: <56389B7E.8090703@intel.com> (raw)
In-Reply-To: <20151103044927.GA4073@localhost.localdomain>
On 03/11/2015 04:49, Jerin Jacob wrote:
> On Tue, Nov 03, 2015 at 12:47:13AM +0100, Jan Viktorin wrote:
>> Hello DPDK community,
>>
>> ARMv7 again, changes:
>>
>> * removed unnecessary code in the #ifndef RTE_FORCE_INTRINSICS .. #endif (atomic, spinlock, byteorder)
>> * more splitting of headers to have 32/64 bit variants (atomic, cpuflags)
>> * fixed cpuflags AT_PLATFORM
>
> Thanks Jan, Dave .
> I will rework on the arm64 support based on this version.
Jerin,
I've got an updated ARMv8 patchset almost ready based on Jan's latest
patchset (v6). Will I post it to the list? I suspect that your patchset
will be the preferred option for acceptance into DPDK, but there may be
one or two snippets of code worth merging together for the final patchset.
Rgds,
Dave.
next prev parent reply other threads:[~2015-11-03 11:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 23:47 Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 01/15] eal/arm: atomic operations for ARM Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 02/15] eal/arm: byte order " Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 03/15] eal/arm: cpu cycle " Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 04/15] eal/arm: implement rdtsc by PMU or clock_gettime Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 05/15] eal/arm: prefetch operations for ARM Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 06/15] eal/arm: spinlock operations for ARM (without HTM) Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 07/15] eal/arm: vector memcpy for ARM Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 08/15] eal/arm: use vector memcpy only when NEON is enabled Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 09/15] eal/arm: cpu flag checks for ARM Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 10/15] eal/arm: detect arm architecture in cpu flags Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 11/15] eal/arm: rwlock support for ARM Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 12/15] eal/arm: add very incomplete rte_vect Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 13/15] gcc/arm: avoid alignment errors to break build Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 14/15] mk: Introduce ARMv7 architecture Jan Viktorin
2015-11-03 10:16 ` Hunt, David
2015-11-03 10:24 ` Bruce Richardson
2015-11-03 11:18 ` Thomas Monjalon
2015-11-03 10:27 ` Jan Viktorin
2015-11-03 11:08 ` Hunt, David
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 15/15] maintainers: claim responsibility for ARMv7 Jan Viktorin
2015-11-03 4:49 ` [dpdk-dev] [PATCH v6 00/15] Support ARMv7 architecture Jerin Jacob
2015-11-03 11:33 ` Hunt, David [this message]
2015-11-03 12:32 ` Jacob, Jerin
2015-11-16 21:33 ` David Marchand
2015-11-18 21:45 ` Thomas Monjalon
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=56389B7E.8090703@intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=viktorin@rehivetech.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).