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: Tue, 15 May 2018 07:24:00 +0100 Message-ID: <147e5200-1a7a-017a-2428-7813ead41ff5@intel.com> References: <777ae6b10a7524e188c07ba14e576fc7b0e21018.1524729978.git.anatoly.burakov@intel.com> <952c259e-eb94-0a8d-7966-00e3591f9c37@intel.com> <456f4736-856e-3b06-4c8c-a74adfd0b723@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: "Burakov, Anatoly" , dev@dpdk.org Return-path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 0C80B1BAB9 for ; Tue, 15 May 2018 08:24:03 +0200 (CEST) In-Reply-To: <456f4736-856e-3b06-4c8c-a74adfd0b723@intel.com> 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 14/05/2018 12:29, Burakov, Anatoly wrote: [..] > This failure is not caused by this patchset, and you should get similar > failures on master if you get these while testing my patchset. I am not > able to reproduce this issue, but i'll double-check the bounded reserve > code with a fine-toothed comb anyway. I reliably get the failure with V3 applied to RC2, but so far haven't been able to replicate with any other combination (clean RC2, RC2+V5, master+V4, etc). Odd..