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 184385F0F; Thu, 20 Dec 2018 15:35:12 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C505321286; Thu, 20 Dec 2018 09:35:11 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 20 Dec 2018 09:35:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=fMQTCkk+9Lj3kPfugrWJTfiHyUy8Re2rtmiqr96K/Fg=; b=RSI6I1D9HnWN FSf55ZgUJiiANHkk6N5kSawKt3oJTvHEeAKaW55jrKDPr8E9uyHTSsd/aEzqa7pv Lkz3gMYjS/cPmhxSmVKWKffgUPPPuo82XlL00IQi4S5V+hdxJZ10zDIUdJdLnj/e hTT5rjqMDy+aM0sym4Q6tdT5RB+idn0= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=fMQTCkk+9Lj3kPfugrWJTfiHyUy8Re2rtmiqr96K/ Fg=; b=sTb5eDEu7DnEtvGOk4UzjR0YMrv0kWa8qbQG4Dgop4xRdScqjg2IYFEbB ObOIgOgGuQXThzZeqLDxoV+MHzKoQUNlYoT7YWydIU6DC+psJBPAN3PK8qV9ZctY 9j9wlPJ4vjNu6/qYVP6zLTk2D3rd4Tb5u49aZkCjyXTaNcIL/faqmajsT2l0C0sw /ZydOWEoqpNQQHI5e1rLIgKg6kDL4h0z7ju24GJcB3YNDSH/mEbhbEZhunnALSAg Pk16vbQw2j4WPYKrqV4U2OeQI6uJNGKPZSEIMOWgkCButXlY1mUnKG/pHKZ1QiRb T61F39HQ7lYJaqsh+mQF/8ZGrWJ9A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudejfedgieejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvffufffkjg hfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcu oehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtd efrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 8893FE4472; Thu, 20 Dec 2018 09:35:10 -0500 (EST) From: Thomas Monjalon To: stable@dpdk.org, Anatoly Burakov Cc: Yongseok Koh , dev , Shahaf Shuler Date: Thu, 20 Dec 2018 15:35:09 +0100 Message-ID: <5100972.CtmhpYIKJZ@xps> In-Reply-To: <8164A185-3807-404C-9678-61513386BB64@mellanox.com> References: <245b643cbfb5f3a0f96e44603339e20278b34e76.1544788410.git.anatoly.burakov@intel.com> <8164A185-3807-404C-9678-61513386BB64@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] malloc: make alignment requirements more stringent 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, 20 Dec 2018 14:35:13 -0000 14/12/2018 19:51, Yongseok Koh: > > > On Dec 14, 2018, at 3:54 AM, Anatoly Burakov wrote: > > > > The external heaps API already implicitly expects start address > > of the external memory area to be page-aligned, but it is not > > enforced or documented. Fix this by implementing additional > > parameter checks at memory add call, and document the page > > alignment requirement explicitly. > > > > Fixes: 7d75c31014f7 ("malloc: allow adding memory to named heaps") > > Cc: stable@dpdk.org > > > > Signed-off-by: Anatoly Burakov > > Suggested-by: Yongseok Koh > > --- > > Acked-by: Yongseok Koh Applied, thanks