From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Sanford, Robert" <rsanford@akamai.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] malloc: fix rte_free run time in O(n) free blocks
Date: Thu, 08 May 2014 23:42:02 +0200 [thread overview]
Message-ID: <8858820.pzz9KGdcSJ@xps13> (raw)
In-Reply-To: <CF916A74.DDD%rsanford@akamai.com>
Hi Robert,
2014-05-08 16:17, Sanford, Robert:
> I haven't heard anything regarding this patch.
> In general, how does your team keep track of outstanding patch requests or
> RFCs?
If nobody complains, it means that everybody agree on the idea.
So it should be accepted after review.
Some patches like this one are not yet reviewed because efforts were focused
on release 1.6.0r2. This enhancement must be integrated in 1.7.0.
I know that patchwork service is desired and I hope it will be available soon.
By the way, looking at librte_malloc, it seems implementation of lists could
be simpler. Don't you think we could improve (in another patch) this whole
code by using BSD macros for lists?
Thanks
--
Thomas
next prev parent reply other threads:[~2014-05-08 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 19:24 Sanford, Robert
2014-05-08 21:17 ` Sanford, Robert
2014-05-08 21:42 ` Thomas Monjalon [this message]
2014-05-09 14:24 ` Sanford, Robert
2014-05-09 14:29 ` 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=8858820.pzz9KGdcSJ@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=rsanford@akamai.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).