From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] malloc: simplify heap initialisation
Date: Wed, 30 Apr 2014 11:47:52 +0200 [thread overview]
Message-ID: <4964655.ZUvISqeXL8@xps13> (raw)
In-Reply-To: <20140418130919.GB4053@localhost.localdomain>
2014-04-18 09:09, Neil Horman:
> On Fri, Apr 18, 2014 at 02:56:18PM +0200, David Marchand wrote:
> > There should be no real need for this initialised field as the whole
> > structure is set to 0 in rte_config_init() by primary process, and
> > secondary processes wait for this to happen before anything else (looking
> > at mem_config magic).
> >
> > Signed-off-by: David Marchand <david.marchand@6wind.com>
>
> Acked-by: Neil Horman <nhorman@tuxdriver.com>
Applied for version 1.6.0r2.
Thanks
--
Thomas
prev parent reply other threads:[~2014-04-30 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 13:50 [dpdk-dev] [PATCH 1/2] mem: add write memory barrier before changing heap state David Marchand
2014-04-15 13:50 ` [dpdk-dev] [PATCH 2/2] mem: fix initialization check for malloc heap David Marchand
2014-04-15 14:08 ` [dpdk-dev] [PATCH 1/2] mem: add write memory barrier before changing heap state Richardson, Bruce
2014-04-16 8:55 ` didier.pallard
2014-04-15 14:44 ` Neil Horman
2014-04-18 12:56 ` [dpdk-dev] [PATCH 0/2] rework heap initialisation David Marchand
2014-04-18 12:56 ` [dpdk-dev] [PATCH 1/2] malloc: get rid of numa_socket field David Marchand
2014-04-18 13:08 ` Neil Horman
2014-04-30 9:46 ` Thomas Monjalon
2014-04-18 12:56 ` [dpdk-dev] [PATCH 2/2] malloc: simplify heap initialisation David Marchand
2014-04-18 13:09 ` Neil Horman
2014-04-30 9:47 ` Thomas Monjalon [this message]
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=4964655.ZUvISqeXL8@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
/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).