From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Robert Sanford <rsanford2@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/2] malloc: fix malloc and free linear complexity
Date: Thu, 26 Jun 2014 14:37:43 +0200 [thread overview]
Message-ID: <3441267.fPINhng712@xps13> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8971A773DD9@IRSMSX103.ger.corp.intel.com>
> From: Robert Sanford
> > Comments on previous versions of this patch:
> > http://dpdk.org/ml/archives/dev/2014-May/002297.html
> > http://dpdk.org/ml/archives/dev/2014-June/003518.html
> >
> > Additional changes from original to v3:
> > * Reduce the minimum-sized block that we put on a free list when
> >
> > splitting a larger block, from 192 to 64. Although memory is
> > plentiful, why waste 64 and 128-byte (plus overhead) blocks?
> >
> > -#define MIN_DATA_SIZE (CACHE_LINE_SIZE * 2)
> > +#define MIN_DATA_SIZE (CACHE_LINE_SIZE)
> >
> > - if (old_elem_size <= MALLOC_ELEM_OVERHEAD + MIN_DATA_SIZE){
> > + if (old_elem_size < MALLOC_ELEM_OVERHEAD + MIN_DATA_SIZE){
> >
> > - if (elem->size - new_size > MIN_DATA_SIZE +
> > MALLOC_ELEM_OVERHEAD){
> > + if (elem->size - new_size >= MIN_DATA_SIZE +
> > MALLOC_ELEM_OVERHEAD){
> >
> > Changes from v2 to v3:
> > * Change the size ranges of the five free lists per heap. The first
> >
> > list will effectively contain blocks of size [64,256].
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Applied for version 1.7.0.
Thanks for this brave rework.
--
Thomas
next prev parent reply other threads:[~2014-06-26 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 12:59 [dpdk-dev] [PATCH v2] " rsanford2
2014-06-17 16:05 ` De Lara Guarch, Pablo
2014-06-17 16:29 ` Robert Sanford
2014-06-23 21:17 ` [dpdk-dev] [PATCH v3 0/2] " Robert Sanford
2014-06-24 14:55 ` De Lara Guarch, Pablo
2014-06-26 12:37 ` Thomas Monjalon [this message]
2014-06-23 21:17 ` [dpdk-dev] [PATCH v3 1/2] " Robert Sanford
2014-06-23 21:17 ` [dpdk-dev] [PATCH v3 2/2] " Robert Sanford
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=3441267.fPINhng712@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=rsanford2@gmail.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).