From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 1AE9F1CBE0 for ; Thu, 5 Apr 2018 16:12:59 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7EF0E2174F; Thu, 5 Apr 2018 10:12:58 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 05 Apr 2018 10:12:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ptxTdLIpZkzcEvvIz+kIdW5U72 7RQAp6S9BJBSjMgZw=; b=KZ2ETbDMpjnlwnXbIRJrO8UogrokOULwV/e9zGaTPA LfVjtelm8b8e+eVbsf/pIosKJYb541Kh6VcoLfm8Vjh5MizVF0qjj2yVjTVrk/z/ 6+ErujoyZ4aaYcyWL/kzlHgxLjYp5qiGROfRFSdCVNJ1VNnp2z/BIS31ecGhkQSE w= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ptxTdL IpZkzcEvvIz+kIdW5U727RQAp6S9BJBSjMgZw=; b=nnH8LOREZ0j+DJEWehmAgQ O0qZvOwotCZr/afzKYphxQ7iONQLOeb7rn8Wf229WyLDu1JiU01xktZgGbB1HXA2 VKJfhk3OVnpZe+yhD7q2xjKX5xND9vGYui18H9aM3uGWnQ8kHRLeQueDZ0lCJH6A wMY8/6fnMYseCH43Ab6CHALoe7kGqDSc+ePa565pcjvE3y/7ltG121xlJPjgI3zq kwWLW4xSCLPrXRfrkNcp0XEIGDrbviwbJYzRVauWGXsdyctfYf9NTwq96mx/4afG 8f6F2YykPsoQcwrwPOz2++R37/Syyh/eGHTRTKjA6K4gt3x2fm+72h5oB6qxy92A == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 5A84BE502E; Thu, 5 Apr 2018 10:12:56 -0400 (EDT) From: Thomas Monjalon To: Shreyansh Jain Cc: Anatoly Burakov , dev@dpdk.org, keith.wiles@intel.com, jianfeng.tan@intel.com, andras.kovacs@ericsson.com, laszlo.vadkeri@ericsson.com, benjamin.walker@intel.com, bruce.richardson@intel.com, konstantin.ananyev@intel.com, kuralamudhan.ramakrishnan@intel.com, louise.m.daly@intel.com, nelio.laranjeiro@6wind.com, yskoh@mellanox.com, pepperjo@japf.ch, jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com, olivier.matz@6wind.com, gowrishankar.m@linux.vnet.ibm.com Date: Thu, 05 Apr 2018 16:12:55 +0200 Message-ID: <2771974.P4zNJljvph@xps> In-Reply-To: <49bcdac0-2631-361d-c454-088c5c70f6b1@nxp.com> References: <49bcdac0-2631-361d-c454-088c5c70f6b1@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 00/68] Memory Hotplug for DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Apr 2018 14:12:59 -0000 05/04/2018 16:24, Shreyansh Jain: > Physical addressing cases for both, dpaa/dpaa2, depend heavily on the > fact that physical addressing was the base and was available in sorted > manner. This is reversed/negated with hotplugging support. > So, rework of both the drivers is required from this perspective. There > are some suggestions floated by Anatoly and internally, but work still > needs to be done. > It also impacts a lot of use-cases for virtualization (no-iommu). So what is your recommendation? Can you rework PA case in dpaa/dpaa2 drivers within 18.05 timeframe?