DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com>
Cc: john.mcnamara@intel.com, jianbo.liu@linaro.org, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples/performance-thread: add arm64 support
Date: Thu, 18 May 2017 00:14:54 +0530	[thread overview]
Message-ID: <20170517184452.GA25743@jerin> (raw)
In-Reply-To: <20170517181949.12002-1-ashwin.sekhar@caviumnetworks.com>

-----Original Message-----
> Date: Wed, 17 May 2017 11:19:49 -0700
> From: Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com>
> To: jerin.jacob@caviumnetworks.com, john.mcnamara@intel.com,
>  jianbo.liu@linaro.org
> Cc: dev@dpdk.org, Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH] examples/performance-thread: add arm64 support
> X-Mailer: git-send-email 2.12.2
> 
> Updated Makefile to allow compilation for arm64 architecture.
> 
> Moved the code for setting the initial stack to architecture specific
> directory.

Please split the patch to two
- "arch_set_stack" abstraction and associated x86 change
- arm64 support

Thanks Ashwin.

I think, This may be the last feature to make arm64 at par with x86 features
supported in DPDK.

/Jerin

  reply	other threads:[~2017-05-17 18:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 18:19 Ashwin Sekhar T K
2017-05-17 18:44 ` Jerin Jacob [this message]
2017-05-18  6:35   ` Jianbo Liu
2017-05-18  7:38     ` Sekhar, Ashwin
2017-05-18  7:34 ` [dpdk-dev] [PATCH v2 0/2] " Ashwin Sekhar T K
2017-05-18  7:34   ` [dpdk-dev] [PATCH v2 1/2] examples/performance-thread: reorganise arch dependent code Ashwin Sekhar T K
2017-05-18  7:34   ` [dpdk-dev] [PATCH v2 2/2] examples/performance-thread: add arm64 support Ashwin Sekhar T K
2017-05-18  8:55     ` Jerin Jacob
2017-05-18  9:00       ` Sekhar, Ashwin
2017-05-18 10:21 ` [dpdk-dev] [PATCH v3 0/2] " Ashwin Sekhar T K
2017-05-18 10:21   ` [dpdk-dev] [PATCH v3 1/2] examples/performance-thread: reorganise arch dependent code Ashwin Sekhar T K
2017-05-18 10:21   ` [dpdk-dev] [PATCH v3 2/2] examples/performance-thread: add arm64 support Ashwin Sekhar T K
2017-07-03 20:57     ` Thomas Monjalon
2017-07-03 21:21       ` O'Driscoll, Tim
2017-07-04  7:37         ` Sekhar, Ashwin
2017-07-04 14:02           ` O'Driscoll, Tim
2017-07-04  8:05 ` [dpdk-dev] [PATCH v4 0/2] " Ashwin Sekhar T K
2017-07-04  8:05   ` [dpdk-dev] [PATCH v4 1/2] examples/performance-thread: reorganise arch dependent code Ashwin Sekhar T K
2017-07-04  8:05   ` [dpdk-dev] [PATCH v4 2/2] examples/performance-thread: add arm64 support Ashwin Sekhar T K
2017-07-04  8:22 ` [dpdk-dev] [PATCH v5 0/2] " Ashwin Sekhar T K
2017-07-04  8:22   ` [dpdk-dev] [PATCH v5 1/2] examples/performance-thread: reorganise arch dependent code Ashwin Sekhar T K
2017-07-04  8:22   ` [dpdk-dev] [PATCH v5 2/2] examples/performance-thread: add arm64 support Ashwin Sekhar T K
2017-07-04 13:20   ` [dpdk-dev] [PATCH v5 0/2] " 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=20170517184452.GA25743@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=ashwin.sekhar@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=jianbo.liu@linaro.org \
    --cc=john.mcnamara@intel.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).