DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>, David Wilder <dwilder@us.ibm.com>
Cc: stable@dpdk.org, dev@dpdk.org, chaozhu@linux.vnet.ibm.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] mem: Fix anonymous mapping on Power9.
Date: Tue, 27 Nov 2018 10:50:21 +0000	[thread overview]
Message-ID: <8e5aa4cb-f972-42a1-1114-bc7beb5aa05d@redhat.com> (raw)
In-Reply-To: <1547076.mggVMYh6Ii@xps>

On 11/18/2018 01:41 PM, Thomas Monjalon wrote:
> 16/11/2018 18:35, 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>
> 
> Applied, thanks
> 
> Note: Cc stable@dpdk.org does not make sense in this context.
> Backporting this patch to 17.11 would be a mistake,
> and 17.08 is probably not in Power9 scope.
> 

I think 17.08 is a typo for 18.08? Anyway, I won't backport to 18.08
unless I hear something further.

> 
> 

  reply	other threads:[~2018-11-27 10:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 17:35 [dpdk-dev] " David Wilder
2018-11-18 13:41 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2018-11-27 10:50   ` Kevin Traynor [this message]
2019-02-18 15:46 ` Thomas Monjalon
2019-02-20  8:07   ` Chao Zhu
2019-02-20 16:04 ` [dpdk-dev] " Burakov, Anatoly
2019-02-20 16:27   ` Thomas Monjalon
2019-02-20 16:44     ` Burakov, Anatoly

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=8e5aa4cb-f972-42a1-1114-bc7beb5aa05d@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=chaozhu@linux.vnet.ibm.com \
    --cc=dev@dpdk.org \
    --cc=dwilder@us.ibm.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).