From: Jason Vassbender <jason.vassbender@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Decoupling DPDK from EAL
Date: Tue, 3 Dec 2013 23:50:44 +0200 [thread overview]
Message-ID: <CALGHckQkBXK6gLks_uiUkrH7z-YxuxiubKBZpa+xrnoT0zm8DQ@mail.gmail.com> (raw)
Hello,
I am trying to integrate DPDK into an existing application in order to
improve packet processing latency, but it is proving rather difficult
because of DPDK's dependency on EAL's thread management and bootstrap
mechanism. Our application already has its own framework for managing
threads and their affinities/priorities, IPC, timers and its own bootstrap
mechanism (not necessarily via command line arguments), we wish to integrate
DPDK as an alternative network back-end, but it wants to to take over our entire
way of doing things.
Are there any plans to decouple DPDK's core functionality away from
EAL so that it can be more easily integrated into existing
applications?
-Jason
next reply other threads:[~2013-12-03 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 21:50 Jason Vassbender [this message]
2013-12-04 8:27 ` François-Frédéric Ozog
2013-12-04 9:25 ` Jason Vassbender
2013-12-04 13:37 ` François-Frédéric Ozog
2013-12-04 14:53 ` Jason Vassbender
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=CALGHckQkBXK6gLks_uiUkrH7z-YxuxiubKBZpa+xrnoT0zm8DQ@mail.gmail.com \
--to=jason.vassbender@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).