From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Olivier MATZ <olivier.matz@6wind.com>,
"Venkatesan, Venky" <venky.venkatesan@intel.com>,
Igor Ryzhov <iryzhov@arccn.ru>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] RTE Ring removing
Date: Wed, 7 May 2014 15:19:22 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772580EFA401D@IRSMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <536A4CB3.9000005@6wind.com>
Hi Oliver,
Just to clarify about mempool - I suppose you are talking about ability to place internal ring and mempool metadata inside externally allocated memory?
It is already possible to keep mempool elements inside externally allocated memory (rte_mempool_xmem_create()).
Konstantin
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier MATZ
Sent: Wednesday, May 07, 2014 4:10 PM
To: Venkatesan, Venky; Igor Ryzhov; dev@dpdk.org
Subject: Re: [dpdk-dev] RTE Ring removing
Hi Venky,
On 05/07/2014 04:01 PM, Venkatesan, Venky wrote:
> We should look at how to make the memseg capable of doing alloc/free
> (including re-assembly of fragments) after the 1.7 release. Is that
> something you are considering doing (or are there any other DPDKers
> considering this), or should I look at putting together a patch for
> that?
No, that's not something I'm working on today.
On this topic, I have some work in progress in the rte_mempool code.
I'll submit it here as soon as it is ready, I'm not sure it will be
finished before the end of the 1.7.0 integration window.
Regards,
Olivier
next prev parent reply other threads:[~2014-05-07 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 9:05 Igor Ryzhov
2014-05-07 7:54 ` Igor Ryzhov
2014-05-07 11:39 ` Olivier MATZ
2014-05-07 12:42 ` Igor Ryzhov
2014-05-07 13:08 ` Olivier MATZ
2014-05-07 14:01 ` Venkatesan, Venky
2014-05-07 15:09 ` Olivier MATZ
2014-05-07 15:19 ` Ananyev, Konstantin [this message]
2014-05-07 15:37 ` Olivier MATZ
2014-05-07 15:36 ` Rogers, Gerald
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=2601191342CEEE43887BDE71AB9772580EFA401D@IRSMSX105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=iryzhov@arccn.ru \
--cc=olivier.matz@6wind.com \
--cc=venky.venkatesan@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).