From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] [PATCH] eal/ppc: fix secondary process to map hugepages in correct order
Date: Tue, 22 Mar 2016 12:11:06 +0000 [thread overview]
Message-ID: <56F1365A.8070709@intel.com> (raw)
In-Reply-To: <2090665.MjcR1UzGxo@xps13>
On 22/03/2016 11:36, Thomas Monjalon wrote:
> Sergio, your help is required here.
I missed it with the /ppc tag.
I'll get to it.
Sergio
> Thanks
>
> 2016-03-17 10:35, gowrishankar:
>> Could this patch be reviewed please.
>>
>> Thanks,
>> Gowrishankar
>>
>> On Monday 07 March 2016 07:43 PM, Gowrishankar wrote:
>>> From: Gowri Shankar <gowrishankar.m@linux.vnet.ibm.com>
>>>
>>> For a secondary process address space to map hugepages from every segment of
>>> primary process, hugepage_file entries has to be mapped reversely from the
>>> list that primary process updated for every segment. This is for a reason that,
>>> in ppc64, hugepages are sorted for decrementing addresses.
>>>
>>> Signed-off-by: Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
>>> ---
>>> lib/librte_eal/linuxapp/eal/eal_memory.c | 26 ++++++++++++++++----------
>>> 1 file changed, 16 insertions(+), 10 deletions(-)
>
next prev parent reply other threads:[~2016-03-22 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 14:13 Gowrishankar
2016-03-17 5:05 ` gowrishankar
2016-03-22 11:36 ` Thomas Monjalon
2016-03-22 12:11 ` Sergio Gonzalez Monroy [this message]
2016-03-22 16:35 ` Sergio Gonzalez Monroy
2016-03-22 17:10 ` Bruce Richardson
2016-05-20 3:03 ` Chao Zhu
2016-05-20 8:01 ` Sergio Gonzalez Monroy
2016-05-20 8:41 ` Chao Zhu
2016-05-20 10:25 ` Sergio Gonzalez Monroy
2017-02-15 8:51 ` Thomas Monjalon
2017-02-16 7:22 ` Chao Zhu
2018-04-15 12:28 ` 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=56F1365A.8070709@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=dev@dpdk.org \
--cc=gowrishankar.m@linux.vnet.ibm.com \
--cc=thomas.monjalon@6wind.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).