From: Robert Sanford <rsanford2@gmail.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] malloc: fix malloc and free linear complexity
Date: Tue, 17 Jun 2014 12:29:06 -0400 [thread overview]
Message-ID: <CA+cr1coP3a6KRBiZwVY20vP_GBsHc=pSqy+NiPsN9y525rTcPQ@mail.gmail.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D897082CBA0C@IRSMSX103.ger.corp.intel.com>
Hi Pablo,
> Overall patch looks OK, but malloc unit tests fail on the last test
(test_multi_alloc_statistics).
> Apparently, the biggest free chunk size changes as it allocates some
memory, whereas in
> the previous implementation, this size did not change. I wonder if unit
test is wrong or if there
> is actually an issue here. Could you look at this as well?
Thanks for your comments. Yes, I will investigate problems with the malloc
unit tests.
BTW, I intend to make one other adjustment to the previous (v2) set of
changes:
--- a/lib/librte_malloc/malloc_elem.c
+++ b/lib/librte_malloc/malloc_elem.c
@@ -143,7 +143,7 @@ split_elem(struct malloc_elem *elem, struct malloc_elem
*split_pt)
size_t
malloc_elem_free_list_index(size_t size)
{
-#define MALLOC_MINSIZE_LOG2 7
+#define MALLOC_MINSIZE_LOG2 8
#define MALLOC_LOG2_INCREMENT 2
--
Robert
next prev parent reply other threads:[~2014-06-17 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 12:59 rsanford2
2014-06-17 16:05 ` De Lara Guarch, Pablo
2014-06-17 16:29 ` Robert Sanford [this message]
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
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='CA+cr1coP3a6KRBiZwVY20vP_GBsHc=pSqy+NiPsN9y525rTcPQ@mail.gmail.com' \
--to=rsanford2@gmail.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).