From: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
To: Dax Rawal <daxayrawal@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] "Re: [RFC PATCH 0/2] dynamic memzones"
Date: Thu, 04 Jun 2015 09:35:51 +0100 [thread overview]
Message-ID: <55700DE7.10403@intel.com> (raw)
In-Reply-To: <CAD6B5uUa+y-LO5Lawfx+DHZA=WvJeFht2ZFDD87WqWyAE899pQ@mail.gmail.com>
On 03/06/2015 20:13, Dax Rawal wrote:
> Hi Sergio,
> >TODOs:
> > - Implement memzone_unreserve, simply call rte_malloc_free.
> > - Implement mempool_delete, simply call rte_memzone_unreserve.
> > - Init heaps with all available memsegs at once.
> > - Review symbols in version map.
> I do not see rte_memzone_unreserve in API documentation. Is this patch already committed so that we have function like rte_mempool_delete()
> Thanks
> Dax
No, it is not merged yet. That was just an RFC, still need to send new
patch with updates/changes.
The feature is expected for 2.1 release if everything goes according to
plan.
Sergio
prev parent reply other threads:[~2015-06-04 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 19:13 Dax Rawal
2015-06-04 8:35 ` Gonzalez Monroy, Sergio [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=55700DE7.10403@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=daxayrawal@gmail.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).