From mboxrd@z Thu Jan  1 00:00:00 1970
From: dwilder <dwilder@us.ibm.com>
Subject: Re: [PATCH] mem: Fix anonymous mapping on Power9.
Date: Fri, 16 Nov 2018 15:56:07 -0800
Message-ID: <c27f600ce7c40a05d732e2d6e6812c94@linux.vnet.ibm.com>
References: <20181114204051.9580-1-dwilder@us.ibm.com>
 <df26df26-6245-10d0-51e7-a03678f5da81@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 8bit
Cc: dev@dpdk.org, stable@dpdk.org, pradeep@us.ibm.com,
 chaozhu@linux.vnet.ibm.com
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com
 [148.163.158.5]) by dpdk.org (Postfix) with ESMTP id CB66A91
 for <dev@dpdk.org>; Sat, 17 Nov 2018 00:53:08 +0100 (CET)
Received: from pps.filterd (m0098419.ppops.net [127.0.0.1])
 by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id
 wAGNnLuD070269 for <dev@dpdk.org>; Fri, 16 Nov 2018 18:53:07 -0500
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154])
 by mx0b-001b2d01.pphosted.com with ESMTP id 2nt6rft9bh-1
 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT)
 for <dev@dpdk.org>; Fri, 16 Nov 2018 18:53:07 -0500
Received: from localhost
 by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only!
 Violators will be prosecuted
 for <dev@dpdk.org> from <dwilder@us.ibm.com>;
 Fri, 16 Nov 2018 23:53:07 -0000
In-Reply-To: <df26df26-6245-10d0-51e7-a03678f5da81@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 2018-11-15 07:11, Burakov, Anatoly wrote:
> On 14-Nov-18 8:40 PM, David Wilder wrote:
> 
>> Please include this patch in 18.11 as well, this patch is not suitable
>> for 17.11.
>> Small note: while this patch is not suitable for 17.11 as is, it can 
>> be made suitable if you drop the memalloc part. I copied this flag 
>> from old memory allocation code, so if 17.11 has this flag there, you 
>> can fix it in 17.11 as well.

Thank you

I am working on a 17.11 fix as well,  the issue is a little different on 
17.11 but removing the flag is indeed part of the fix.