From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dwilder@us.ibm.com> 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 Received: from b03cxnp07029.gho.boulder.ibm.com (9.17.130.16) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Fri, 16 Nov 2018 23:53:04 -0000 Received: from b03ledav005.gho.boulder.ibm.com (b03ledav005.gho.boulder.ibm.com [9.17.130.236]) by b03cxnp07029.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id wAGNr3gX19529734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 16 Nov 2018 23:53:03 GMT Received: from b03ledav005.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B78CFBE051; Fri, 16 Nov 2018 23:53:03 +0000 (GMT) Received: from b03ledav005.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7ACD1BE054; Fri, 16 Nov 2018 23:53:03 +0000 (GMT) Received: from ltc.linux.ibm.com (unknown [9.16.170.189]) by b03ledav005.gho.boulder.ibm.com (Postfix) with ESMTP; Fri, 16 Nov 2018 23:53:03 +0000 (GMT) MIME-Version: 1.0 Date: Fri, 16 Nov 2018 15:56:07 -0800 From: dwilder <dwilder@us.ibm.com> To: "Burakov, Anatoly" <anatoly.burakov@intel.com> Cc: dev@dpdk.org, stable@dpdk.org, pradeep@us.ibm.com, chaozhu@linux.vnet.ibm.com In-Reply-To: <df26df26-6245-10d0-51e7-a03678f5da81@intel.com> References: <20181114204051.9580-1-dwilder@us.ibm.com> <df26df26-6245-10d0-51e7-a03678f5da81@intel.com> X-Sender: dwilder@us.ibm.com User-Agent: Roundcube Webmail/1.0.1 X-TM-AS-GCONF: 00 x-cbid: 18111623-0020-0000-0000-00000E8AFFFD X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00010064; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000270; SDB=6.01118491; UDB=6.00580222; IPR=6.00898600; MB=3.00024199; MTD=3.00000008; XFM=3.00000015; UTC=2018-11-16 23:53:06 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18111623-0021-0000-0000-000063BCDA26 Message-Id: <c27f600ce7c40a05d732e2d6e6812c94@linux.vnet.ibm.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 8bit X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-16_12:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=917 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1811160211 Subject: Re: [dpdk-dev] [PATCH] mem: Fix anonymous mapping on Power9. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list 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> X-List-Received-Date: Fri, 16 Nov 2018 23:53:09 -0000 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.