From: Nicolas Pernas Maradei <nico@emutex.com>
To: dev@dpdk.org
Subject: [dpdk-dev] mempool re-initialization
Date: Wed, 20 Aug 2014 09:56:14 +0100 [thread overview]
Message-ID: <53F462AE.2010509@emutex.com> (raw)
Hi,
At mempool creation time you can pass in a callback function to
rte_mempool_create() that DPDK will call for every mbuf on the mempool
so you can initialize them to your liking. However, there doesn't seem
to be a straight forward way do that again once the mempool is already
created though.
I'm wondering if there's a clean/nice way to re-initialize all mempool's
mbufs once the mempool's been created?
I was thinking on something like retrieving all mbufs one by one, do my
re-initialization and then put them back into the mempool. I'd have to
make sure of getting all mbufs out before start putting them back again
to avoid the cache, but that'd be OK. Of course this won't be on the
fast-path.
Is there a cleaner way to do this? Any suggestion?
Thanks,
Nico.
--
Nicolás Pernas Maradei
Software Engineer
Emutex Ltd.
reply other threads:[~2014-08-20 8:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53F462AE.2010509@emutex.com \
--to=nico@emutex.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).