From: Stephen Hemminger <stephen@networkplumber.org>
To: Charles Ju <charlesyju@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Using dpdk libraries without EAL
Date: Thu, 13 Sep 2018 07:47:01 -0700 [thread overview]
Message-ID: <20180913074701.3290d8c2@xeon-e3> (raw)
In-Reply-To: <CAODH1pdn=fpFP2cf8283ZFP5L0Ay87nxAAhDtNjvOQ9c5_cmFw@mail.gmail.com>
On Mon, 10 Sep 2018 16:05:33 +0800
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?
If you are going to extract bits and pieces then you are going to have
to look at the internals of the source code. And deal with future changes.
I don't think it is fair to developers to expect that cherry picking libraries
will work.
next prev parent reply other threads:[~2018-09-13 14:47 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
2018-09-13 14:47 ` Stephen Hemminger [this message]
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=20180913074701.3290d8c2@xeon-e3 \
--to=stephen@networkplumber.org \
--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).