From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id C3C4B1BD98 for <dev@dpdk.org>; Mon, 14 May 2018 02:01:32 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CDCBA24EEF; Sun, 13 May 2018 20:01:30 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 13 May 2018 20:01:30 -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=GJtfMXOpHnqDUazreF59ydJcK2 K8ObEwaGYfBBonesw=; b=T/gv8emZCPpRWLBikC4fdhOPC6xTJUYQYcWdGSc+cJ Fxr5iLnnS0VlmfexTSsei+MJ7G5MlHetyk5lTHc3F5OGTfIUuolf0uvXoq/ZDbbm 8Yc1cMmS8cnZWZb+1lKZVIESnCT9w6anNklBFNCFi9YidlbzVaI/9/dU/kBBueXE 0= 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=GJtfMX OpHnqDUazreF59ydJcK2K8ObEwaGYfBBonesw=; b=fSwmYPV/Z6FL8qaDKiF/5z 3c99qEmaCYJECefK0GyRICeDuViA974JlVQSP5ZKykI/91qTNr3F/8UyrVQ41Iss 029UfJlPigoaQuzHXqTe+sIVqqLZpCItg6aMIeSXC/wvAt+jhBC76wMfzQmmHkne yV6vTVX5vsGFnyWgJxgAsQDiAktQXkSj7s63jDt2vqN9SOXh4WBbshW2SDf9G7+8 /jfO1GrvXVYxj/tb0L8Uq/ldZvVlwiuScowGZ7cHIh/8sqC8GQP6eDvLXg3T6b5t hmIz0Bs41o1LGFJi9cZuUG3P5iw+ExA9CF+J2NOerMHSQ2qRmx+Ss3Ex+LcCSAdQ == X-ME-Sender: <xms:2tH4WgK1ELepThn5Dd-yMi-nNJhEStgQXgEZJbeG7YphgR6tP2tzWA> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 4CDEDE47F2; Sun, 13 May 2018 20:01:30 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: Anatoly Burakov <anatoly.burakov@intel.com> Cc: dev@dpdk.org Date: Mon, 14 May 2018 02:01:29 +0200 Message-ID: <33184831.MgCL7t9TaC@xps> In-Reply-To: <c60cdb01eedd3f02922c776d22a9d28be28a6b9c.1525364731.git.anatoly.burakov@intel.com> References: <c60cdb01eedd3f02922c776d22a9d28be28a6b9c.1525364731.git.anatoly.burakov@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] memzone: document reserving zero-length memzones 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://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Mon, 14 May 2018 00:01:33 -0000 03/05/2018 18:25, Anatoly Burakov: > Currently, reserving a memzone with length set to 0 will not trigger > any memory allocations, and memzone will instead be looking through > already allocated memory only. Document this limitation. > > Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Applied, thanks