From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id D12955B34
 for <dev@dpdk.org>; Wed, 17 Oct 2018 00:27:48 +0200 (CEST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 3126021E3E;
 Tue, 16 Oct 2018 18:27:48 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
 by compute1.internal (MEProxy); Tue, 16 Oct 2018 18:27:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 from:to:cc:subject:date:message-id:mime-version
 :content-transfer-encoding:content-type; s=mesmtp; bh=FoFxoNCSTR
 MMqGiIVL7XVaOdEwcIsvw25vM+S5HMeXI=; b=lbSgzdYWOEGae9rNwOABGiBnQk
 qrMU6z6XfiDgKHRLM7qtygCPGfUGvUmKkFZkOR29tUC+X6ZK6SALXQ4ui/U8A/bN
 5UZdvBHzYuTUTZ4/IN0IC4XteWke2WjZb4dLkBXlcnc7qUjbavadoC7RirjU+LLl
 qFNOEVDyawtGKNvU8=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:message-id:mime-version:subject:to:x-me-proxy
 :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=FoFxoN
 CSTRMMqGiIVL7XVaOdEwcIsvw25vM+S5HMeXI=; b=BCfnWCT9oFqJcU5O6AB3ys
 fOxdeD9BfFPpTw7Z6OdShIJFd82VUCEk3aEehvQJca7c3+umoW8KMDbwe8m9/ofi
 aLGEN5yfzF573Vb3j22aXdmTGHkyngV906N4YZiOekf9tXii1IqswWtTUNul1JSq
 w/+Nwjw6QniTKO5vweEdYaPoUka8coUTuXdf2dwDHjk/A2iHJHYJttZHY8OSVxlp
 VS0pbkuXIB0OwlO2Oronp/bhbPM15YSd/QeBzqz2KXwDszjNs3vM5MI/VKCSrTWc
 XyeOOwt1NL3FUmsCsk26gfdVyQXj+2sidjpVhWFPY0wc+MzNuVan+z7CGA6cqxEA
 ==
X-ME-Sender: <xms:42XGW6Bzkl-obc_ztX2aMSfYT90yab0R8y6gi3PCHduGs6JLAM_AdQ>
X-ME-Proxy: <xmx:42XGW6upWsHRGvgI3scXMpxeyc52SLJXF2MehpdVFMD3vRAdmz8Q9Q>
 <xmx:42XGW8_Cm_VG3FFrCnztSML9DQn2-KHvxlxokH_vD67kChffME1TSQ>
 <xmx:42XGW4bf8TqoDajnRc7AKudOW557gs7ISwRGe09TzkvSRoWI2ZKrvA>
 <xmx:42XGW6rdzXLJd9JFS-EMM19wGzQbq3H-0tuGiWX4Z18CV-rHl8W3Ag>
 <xmx:42XGW91kBsyGl-u_jCIF1QXnt8rDtwT4gFDNfGhr5YSOuOjITgHd6Q>
 <xmx:5GXGW-do76h8WeDPie1xQPzxrJ7tm9Bkf2-Epy2u3H7zIY7iBZ4rJQ>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 4CC8AE43A6;
 Tue, 16 Oct 2018 18:27:47 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: shreyansh.jain@nxp.com
Cc: dev@dpdk.org
Date: Wed, 17 Oct 2018 00:27:50 +0200
Message-ID: <1642576.7uxZiAvKvM@xps>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: [dpdk-dev] dpaax warnings
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: Tue, 16 Oct 2018 22:27:49 -0000

Hi Shreyansh,

When initializing DPDK on x86, we get those warnings:
	dpaax: Unable to glob device-tree memory node: (/proc/device-tree/memory[@0-9]*/reg)(3)
	dpaax: PA->VA translation not available;
	dpaax: Expect performance impact.

Is it possible to avoid running dpaax init when not available?