From: "Wiles, Keith" <keith.wiles@intel.com>
To: Charles Ju <charlesyju@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Using dpdk libraries without EAL
Date: Thu, 13 Sep 2018 14:45:40 +0000 [thread overview]
Message-ID: <3FB567AB-87F7-46F2-8D45-786C86D3CC63@intel.com> (raw)
In-Reply-To: <CAODH1pdn=fpFP2cf8283ZFP5L0Ay87nxAAhDtNjvOQ9c5_cmFw@mail.gmail.com>
> On Sep 10, 2018, at 3:05 AM, Charles Ju <charlesyju@gmail.com> wrote:
>
> Hi,
>
> I have developed my own packet capture code and would like to just use the
> dpdk libraries such as the ACL Library and mempool libraries. In this case,
> does these libraries require the EAL?
It depends on the code, but I assume it is using the DPDK memory system rte_malloc() and the like.
You will have to replace these calls as the memory subsystem is inited from EAL. Also I assume it maybe calling into other library components and they will have to modified as well.
DPDK is not a collection of functions like libc. The libc library is a collection of functions that are pretty much independent from each other and easy to use in a standalone fashion. DPDK Libraries are not typically written to be standalone as they use other highly optimized routines in DPDK.
It is not to say we should not look at making some parts of DPDK replaceable or be able to be swapped out with other user components. We have done a lot of work to allow external memory managers or hardware based memory in the case of SOCs.
Regards,
Keith
next prev parent reply other threads:[~2018-09-13 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 8:05 Charles Ju
2018-09-13 14:45 ` Wiles, Keith [this message]
2018-09-13 14:47 ` Stephen Hemminger
2018-09-10 8:20 Charles Ju
2018-09-10 12:38 ` Wiles, Keith
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=3FB567AB-87F7-46F2-8D45-786C86D3CC63@intel.com \
--to=keith.wiles@intel.com \
--cc=charlesyju@gmail.com \
--cc=users@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).