From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 94050201 for ; Sun, 23 Sep 2018 23:21:14 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B9CB620D8D; Sun, 23 Sep 2018 17:21:13 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 23 Sep 2018 17:21:13 -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=kAuTAZVyEAr+v0nluz2XZRPwE1 jzt3aiT6iwV5iY3nM=; b=R/Ro+kV0YLk2D2ju2zRqWx4G6bNPYNAkYyeo1JCA2b kCbPPUEG4++hhv56CgPBrJXI9xYYIFsRpq4KA/wnZYLo/Z/QN/m/dcTnRYlrjFWp Zi35z4RUPIJoA+4Wtffr5OYOzugkwVEKmlk44bZ1NxaxLScb+Ax14Elex9KSiZry Y= 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=fm3; bh=kAuTAZ VyEAr+v0nluz2XZRPwE1jzt3aiT6iwV5iY3nM=; b=NbwV9flJ4q+VaDDS0rk2FR uT3aaLtxGdQ2inuvCJkga4g55tOnYw/S1RbjYAwEbL6hdmUlU6AD0B4mpsS0heNm 0ZW3XjJDbJhKneV7gJXRuJKinBXIB4iRhHsNm2V1kGAUqE61EEumi94tHoYpQ61g 6A0+9CgfhXP74UzvQT03jEbGOTGzPIgusVI+41jTH09zRE77HnF7JqlKtysd2zwg wBRIgIYOKXUVD6wEWc6LLFgFY9+wFtQvAja3RmalqEtYc/ig7Ou5v+soHoL5TT4E BNfq7vbo+XpiSUe+ERobtXav4eHL2+RIVOafci8neD4u6SXkSTa0atNNplGGoMIg == X-ME-Proxy: 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 03B86E462B; Sun, 23 Sep 2018 17:21:10 -0400 (EDT) From: Thomas Monjalon To: Anatoly Burakov Cc: dev@dpdk.org, laszlo.madarassy@ericsson.com, laszlo.vadkerti@ericsson.com, andras.kovacs@ericsson.com, winnie.tian@ericsson.com, daniel.andrasi@ericsson.com, janos.kobor@ericsson.com, geza.koblo@ericsson.com, srinath.mannam@broadcom.com, scott.branden@broadcom.com, ajit.khaparde@broadcom.com, keith.wiles@intel.com, bruce.richardson@intel.com, shreyansh.jain@nxp.com, shahafs@mellanox.com, arybchenko@solarflare.com Date: Sun, 23 Sep 2018 23:21:09 +0200 Message-ID: <2407291.ybRTbF1rkB@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4 00/20] Support externally allocated memory in 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: Sun, 23 Sep 2018 21:21:14 -0000 Hi Anatoly, 21/09/2018 18:13, Anatoly Burakov: > This is a proposal to enable using externally allocated memory > in DPDK. About this change and previous ones, I think we may miss some documentation about the usage and the internal design of the DPDK memory allocation. You already updated some doc recently: http://git.dpdk.org/dpdk/commit/?id=b31739328 This is what we have currently: http://doc.dpdk.org/guides/prog_guide/env_abstraction_layer.html#memory-segments-and-memory-zones-memzone http://doc.dpdk.org/guides/prog_guide/env_abstraction_layer.html#malloc http://doc.dpdk.org/guides/prog_guide/mempool_lib.html This is probably a good time to check this doc again. Do you think it deserves more explanations, or maybe some figures?