From: Tomas Vestelind <Tomas.Vestelind@hiq.se>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Calling rte_eal_init multiple times in the same process
Date: Thu, 17 Apr 2014 09:09:44 +0000 [thread overview]
Message-ID: <EA933124232C9B42A1CD6FA8FCA48B4B279DA1@HIQQBEXC101.sto.hiq.se> (raw)
Dear all,
I'm not sure who to address with this email so I'll just present my problem and my suggested solution.
The problem I'm facing is that I need to do rte_eal_init serveral times in the same process. The reason for this is mostly architectural as we want to divide certain functionality in to different, implementation independent, modules in which DPDK would be used for different purposes. Thus we would need to eventually call rte_eal_init several times because we can't say for sure if it has been called by another module or not.
While thinking about it I saw no good, existing solution to this (I might have missed it though). Would returning a "DPDK has already been initialized" error code in rte_eal_init be a good way to go about it? I haven't done this yet but I could probably provide a patch if it's interesting.
Thank you for your time and a very nice framework with good documentation!
BR,
Tomas
next reply other threads:[~2014-04-17 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 9:09 Tomas Vestelind [this message]
2014-04-17 9:44 ` Thomas Monjalon
2014-04-17 11:06 ` Neil Horman
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=EA933124232C9B42A1CD6FA8FCA48B4B279DA1@HIQQBEXC101.sto.hiq.se \
--to=tomas.vestelind@hiq.se \
--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).