From: David Marchand <david.marchand@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] rework heap initialisation
Date: Fri, 18 Apr 2014 14:56:16 +0200 [thread overview]
Message-ID: <1397825778-24334-1-git-send-email-david.marchand@6wind.com> (raw)
In-Reply-To: <20140415144440.GD3557@hmsreliant.think-freely.org>
Following Neil's suggestion, here is a patchset that removes the need for a
synchronisation mechanism when initialising heap objects.
As a consequence, this patchset replaces the two patches Didier proposed
earlier.
--
David Marchand
David Marchand (2):
malloc: get rid of numa_socket field
malloc: simplify heap initialisation
lib/librte_eal/common/include/rte_malloc_heap.h | 8 ----
lib/librte_malloc/malloc_heap.c | 46 +++--------------------
2 files changed, 5 insertions(+), 49 deletions(-)
--
1.7.10.4
next prev parent reply other threads:[~2014-04-18 12:56 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 ` David Marchand [this message]
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
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=1397825778-24334-1-git-send-email-david.marchand@6wind.com \
--to=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).