From: Thomas Monjalon <thomas@monjalon.net>
To: David Wilder <dwilder@us.ibm.com>
Cc: dev@dpdk.org, stable@dpdk.org, pradeep@us.ibm.com,
chaozhu@linux.vnet.ibm.com, techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mem: Fix anonymous mapping on Power9.
Date: Thu, 15 Nov 2018 19:17:14 +0100 [thread overview]
Message-ID: <10862745.IQX0Zpk1jJ@xps> (raw)
In-Reply-To: <20181114204051.9580-1-dwilder@us.ibm.com>
Hi,
14/11/2018 21:40, David Wilder:
> Removed the use of MAP_HUGETLB for anonymous mapping on ppc64. The
> MAP_HUGETLB had previously been added to workaround issues on IBM Power8
> systems when mapping /dev/zero (see: commit
> 284ae3e9ff9a92575c28c858efd2c85c8de6d440). In the current code the
> MAP_HUGETLB flag will cause the anonymous mapping to fail on Power9.
> Note, Power8 is currently failing to correctly mmap Hugepages, with and
> without this change.
>
> Signed-off-by: David Wilder <dwilder@us.ibm.com>
> Reviewed-by: Pradeep Satyanarayana <pradeep@us.ibm.com>
> ---
> This patch corrects problems with virtual address mapping on IBM Power9 system.
> I have tested with primary and secondary process tests. IBM power8 systems
> continue to fail with and without this change. I am perusing a fix for power8
> and will post a patch when its working. As Power9 is our primary platform I
> wanted to get this patch out. I will follow up with a power8 fix when its ready.
We need to document that Power8 is not supported in DPDK 18.11.
Please send a patch to explain it in "known issues":
http://doc.dpdk.org/guides/rel_notes/release_18_11.html#known-issues
We may also note that IBM POWER support is in alpha stage:
http://git.dpdk.org/dpdk/tree/MAINTAINERS#n236
Thanks in advance
prev parent reply other threads:[~2018-11-15 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 20:40 David Wilder
2018-11-15 10:49 ` Burakov, Anatoly
2018-11-15 15:11 ` Burakov, Anatoly
2018-11-16 23:56 ` dwilder
2018-11-15 18:17 ` Thomas Monjalon [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=10862745.IQX0Zpk1jJ@xps \
--to=thomas@monjalon.net \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
--cc=dwilder@us.ibm.com \
--cc=pradeep@us.ibm.com \
--cc=stable@dpdk.org \
--cc=techboard@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).