From: Alain Gautherot <alain@edicogenome.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Building a DPDK application with librte_malloc only?
Date: Sat, 23 Jan 2016 00:11:52 +0000 [thread overview]
Message-ID: <BY2PR07MB057BE9ED533C967B442F5DFB1C50@BY2PR07MB057.namprd07.prod.outlook.com> (raw)
Hello,
I'm using DPDK2.0.0 to test memory allocation and have couple questions:
1) Is it possible to build an application with only rte_malloc (and not the other libraries/services)?
I didn't find anything in the documentation.
2) Is it possible to use DPDK on CPUs that don't have AES-NI?
Is there a way to disable that in DPDK so I can run on more mainstream CPUs?
Maybe a CONFIG_* (but couldn't find it)?
Thanks,
Alain
--
Alain Gautherot
Edico Genome
3344 North Torrey Pines Court, Plaza Level
La Jolla, CA 92037
www.edicogenome.com
next reply other threads:[~2016-01-23 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 0:11 Alain Gautherot [this message]
2016-01-25 13:47 ` Sergio Gonzalez Monroy
2016-01-25 21:01 ` Alain Gautherot
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=BY2PR07MB057BE9ED533C967B442F5DFB1C50@BY2PR07MB057.namprd07.prod.outlook.com \
--to=alain@edicogenome.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).