From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Chao Zhu <chaozhu@linux.vnet.ibm.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>,
"Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>,
"david.marchand@6wind.com" <david.marchand@6wind.com>
Subject: Re: [PATCH 2/2] doc/guides: Add hugepage reserve instructions for IBM POWER
Date: Thu, 6 Apr 2017 16:16:29 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2332B24A5@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1491473170-25160-3-git-send-email-chaozhu@linux.vnet.ibm.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Chao Zhu
> Sent: Thursday, April 6, 2017 11:06 AM
> To: dev@dpdk.org
> Cc: Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>; Gonzalez Monroy,
> Sergio <sergio.gonzalez.monroy@intel.com>; david.marchand@6wind.com
> Subject: [dpdk-dev] [PATCH 2/2] doc/guides: Add hugepage reserve
> instructions for IBM POWER
>
> This patch adds additional instructions for hugepage reservation on IBM
> POWER.
>
> Signed-off-by: Chao Zhu <chaozhu@linux.vnet.ibm.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
prev parent reply other threads:[~2017-04-06 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 10:06 [PATCH 0/2] ppc:Fix the memory initialization for IBM POWER Chao Zhu
2017-04-06 10:06 ` [PATCH 1/2] eal/ppc: fix mmap for memory initialization Chao Zhu
2017-04-06 12:58 ` Sergio Gonzalez Monroy
2017-04-13 1:40 ` Chao Zhu
2017-04-13 8:14 ` Sergio Gonzalez Monroy
2017-04-20 7:41 ` Thomas Monjalon
2017-04-20 7:39 ` Thomas Monjalon
2017-04-06 10:06 ` [PATCH 2/2] doc/guides: Add hugepage reserve instructions for IBM POWER Chao Zhu
2017-04-06 16:16 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE2332B24A5@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=gowrishankar.m@linux.vnet.ibm.com \
--cc=sergio.gonzalez.monroy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.