From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lewis Donzis <lew@perftech.com>
Subject: Re: [dpdk-users] rte_zmalloc() returning non-zeroed
	memory on FreeBSD
Date: Fri, 4 Nov 2016 11:43:49 -0500
Message-ID: <8B6A4BDB-FD30-46FA-9034-29BF7C2D4152@perftech.com>
References: <44ECBB6D-0B65-46D0-AAE5-E96E3F8CB59A@perftech.com>
 <112cd7ac-2dde-3e1b-0fc1-f21f3c253982@intel.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: dev@dpdk.org
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from smtp-gw.pt.net (smtp-gw.pt.net [206.210.194.15])
 by dpdk.org (Postfix) with ESMTP id 1160329CF
 for <dev@dpdk.org>; Fri,  4 Nov 2016 17:44:51 +0100 (CET)
In-Reply-To: <112cd7ac-2dde-3e1b-0fc1-f21f3c253982@intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://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: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>


> On Nov 4, 2016, at 11:38 AM, Sergio Gonzalez Monroy =
<sergio.gonzalez.monroy@intel.com> wrote:
>=20
> On 03/11/2016 20:04, Lewis Donzis wrote:
>> I=E2=80=99m curious about how/whether this got resolved.  The 16.07.1 =
code doesn=E2=80=99t appear to have this fixed.
>>=20
>> Is it still forthcoming?
>>=20
>> Thanks,
>> lew
>=20
> It should have been fixed in 16.07.1.
> =
http://dpdk.org/browse/dpdk-stable/commit/?id=3D82f931805506efbb8b5046e904=
5bec8f04bbabf6
>=20
> Do you have an easy test to reproduce? can you reproduce it with any =
of the app/examples?

Oh, sorry, I was looking at the rte_zmalloc() code, assuming it would be =
changed there, but it looks like the commit was to change contigmem =
instead, which seems perfectly logical and reasonable.

It=E2=80=99s entirely possible that the folks here who tested 16.07.1 =
forgot to replace the contigmem driver, so perhaps that is the problem.

We=E2=80=99ll check it out and report back.

Thanks!
lew=