From: "Mauricio Vásquez" <mauricio.vasquezbernal@studenti.polito.it>
To: dev@dpdk.org
Subject: [dpdk-dev] Why rte_eal_ivshmem_obj_initd() does not add memory pools to rte_mempool_tailq list?
Date: Thu, 15 Oct 2015 18:45:37 +0200 [thread overview]
Message-ID: <CAPwdgqh_MPTv_VbQN2GEh_EtZyPH2=dY9KM-9za_tbKZn4HtbQ@mail.gmail.com> (raw)
Dear DPDK community,
Some time ago I was trying to map a memory pool into a guest using IVSHMEM
as described here:
http://comments.gmane.org/gmane.comp.networking.dpdk.devel/17779
After some time I decided to review the code of eal_ivshmem.c, I noticed
that in the function rte_eal_ivshmem_obj_init the rings are added to the
rte_ring_tailq list, but for memory pools there is not a similar procedure.
My question is why it does not exist such procedure? Is there any reason or
is it just missing?
If it is just missing I could propose a implementation for it,
Thank you very much for your attention,
Mauricio Vásquez
next reply other threads:[~2015-10-15 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 16:45 Mauricio Vásquez [this message]
2015-10-16 13:00 ` Burakov, Anatoly
2015-10-16 13:16 ` Mauricio Vásquez
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='CAPwdgqh_MPTv_VbQN2GEh_EtZyPH2=dY9KM-9za_tbKZn4HtbQ@mail.gmail.com' \
--to=mauricio.vasquezbernal@studenti.polito.it \
--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).