From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Chao Zhu <bjzhuc@cn.ibm.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 00/12] Patches for DPDK to support Power architecture
Date: Thu, 13 Nov 2014 11:24:35 +0100 [thread overview]
Message-ID: <235979634.ZQM3me8EPh@xps13> (raw)
In-Reply-To: <1411724186-8036-1-git-send-email-bjzhuc@cn.ibm.com>
Hi Chao,
2014-09-26 05:36, Chao Zhu:
> The set of patches add IBM Power architecture to the DPDK. It adds the required support to the
> EAL library. This set of patches doesn't support full function on Power processors. Many functions
> are turned off in configuratidon. More patches will be added continuesly.
>
> Chao Zhu (12):
> Add compiling definations for IBM Power architecture
> Add atomic operations for IBM Power architecture
> Add byte order operations for IBM Power architecture
> Add CPU cycle operations for IBM Power architecture
> Add prefetch operation for IBM Power architecture
> Add spinlock operation for IBM Power architecture
> Add vector memcpy for IBM Power architecture
> Add CPU flag checking for IBM Power architecture
> Remove iopl operation for IBM Power architecture
> Add cache size define for IBM Power Architecture
> Add huge page sizes for IBM Power architecture
> Add memory support for IBM Power Architecture
Could you share the status of the rework of these patches?
Maybe that some parts could enter in 1.8 as a preview.
--
Thomas
next prev parent reply other threads:[~2014-11-13 10:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 9:36 Chao Zhu
2014-09-26 9:36 ` [dpdk-dev] [PATCH 01/12] Add compiling definations for IBM " Chao Zhu
2014-09-26 9:36 ` [dpdk-dev] [PATCH 02/12] Add atomic operations " Chao Zhu
2014-09-29 6:16 ` Hemant
2014-09-29 6:41 ` Chao CH Zhu
2014-10-16 0:39 ` Ananyev, Konstantin
2014-10-16 3:14 ` Chao CH Zhu
2014-10-16 9:42 ` Richardson, Bruce
2014-10-16 11:04 ` Ananyev, Konstantin
[not found] ` <2601191342CEEE43887BDE71AB97725821393F5D@IRSMSX105.ger.corp.intel.com>
2014-10-16 10:59 ` Ananyev, Konstantin
2014-09-26 9:36 ` [dpdk-dev] [PATCH 03/12] Add byte order " Chao Zhu
2014-09-26 9:36 ` [dpdk-dev] [PATCH 04/12] Add CPU cycle " Chao Zhu
2014-09-26 9:36 ` [dpdk-dev] [PATCH 05/12] Add prefetch operation " Chao Zhu
2014-09-26 9:36 ` [dpdk-dev] [PATCH 06/12] Add spinlock " Chao Zhu
2014-09-26 9:36 ` [dpdk-dev] [PATCH 07/12] Add vector memcpy " Chao Zhu
2014-09-26 9:36 ` [dpdk-dev] [PATCH 08/12] Add CPU flag checking " Chao Zhu
2014-09-26 9:36 ` [dpdk-dev] [PATCH 09/12] Remove iopl operation " Chao Zhu
2014-10-06 22:03 ` Cyril Chemparathy
2014-10-07 14:46 ` Ananyev, Konstantin
2014-10-13 2:33 ` Chao CH Zhu
2014-09-26 9:36 ` [dpdk-dev] [PATCH 10/12] Add cache size define for IBM Power Architecture Chao Zhu
2014-09-29 6:21 ` Hemant
2014-09-26 9:36 ` [dpdk-dev] [PATCH 11/12] Add huge page sizes for IBM Power architecture Chao Zhu
2014-09-26 9:36 ` [dpdk-dev] [PATCH 12/12] Add memory support for IBM Power Architecture Chao Zhu
2014-11-13 10:24 ` Thomas Monjalon [this message]
2014-11-13 10:31 ` [dpdk-dev] [PATCH 00/12] Patches for DPDK to support Power architecture 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=235979634.ZQM3me8EPh@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=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).