From mboxrd@z Thu Jan 1 00:00:00 1970 From: Remy Horton Subject: Re: [PATCH v3 3/3] memzone: improve zero-length memzone reserve Date: Fri, 11 May 2018 11:25:39 +0100 Message-ID: References: <777ae6b10a7524e188c07ba14e576fc7b0e21018.1524729978.git.anatoly.burakov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: sergio.gonzalez.monroy@intel.com To: Anatoly Burakov , dev@dpdk.org Return-path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 82DDA1B28B for ; Fri, 11 May 2018 12:25:42 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 03/05/2018 18:18, Anatoly Burakov wrote: [..] > Also, fixup unit tests to account for the new behavior. Tried running the tests but it fails on a boundary check: RTE>>memzone_autotest test basic memzone API [...] 1GB Huge pages available test alignment for memzone_reserve check alignments and lengths check overlapping test boundary alignment for memzone_reserve check_memzone_bounded(MZ_TEST_bounded_128): invalid memzone boundary 128 crossed Test Failed RTE>>