From: Lewis Donzis <lew@perftech.com>
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-users] rte_zmalloc() returning non-zeroed memory on FreeBSD
Date: Fri, 4 Nov 2016 15:10:23 -0500 [thread overview]
Message-ID: <FF8285AF-ECE3-4F4B-B894-7073A19AB44C@perftech.com> (raw)
In-Reply-To: <112cd7ac-2dde-3e1b-0fc1-f21f3c253982@intel.com>
> On Nov 4, 2016, at 11:38 AM, Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> wrote:
> It should have been fixed in 16.07.1.
> http://dpdk.org/browse/dpdk-stable/commit/?id=82f931805506efbb8b5046e9045bec8f04bbabf6
Hi, Sergio.
We confirmed that it works perfectly with 16.07.1 with the new contigmem driver.
Thanks!
lew
next prev parent reply other threads:[~2016-11-04 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 20:04 Lewis Donzis
2016-11-04 16:38 ` Sergio Gonzalez Monroy
2016-11-04 16:43 ` Lewis Donzis
2016-11-04 20:10 ` Lewis Donzis [this message]
[not found] <1470871839.40000.48.camel@intel.com>
2016-08-11 7:05 ` Thomas Monjalon
2016-08-15 17:23 ` Harris, James R
2016-08-16 7:36 ` Sergio Gonzalez Monroy
2016-08-16 22:54 ` Harris, James R
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FF8285AF-ECE3-4F4B-B894-7073A19AB44C@perftech.com \
--to=lew@perftech.com \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).