* [dpdk-users] Building a DPDK application with librte_malloc only?
@ 2016-01-23 0:11 Alain Gautherot
2016-01-25 13:47 ` Sergio Gonzalez Monroy
0 siblings, 1 reply; 3+ messages in thread
From: Alain Gautherot @ 2016-01-23 0:11 UTC (permalink / raw)
To: users
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-users] Building a DPDK application with librte_malloc only?
2016-01-23 0:11 [dpdk-users] Building a DPDK application with librte_malloc only? Alain Gautherot
@ 2016-01-25 13:47 ` Sergio Gonzalez Monroy
2016-01-25 21:01 ` Alain Gautherot
0 siblings, 1 reply; 3+ messages in thread
From: Sergio Gonzalez Monroy @ 2016-01-25 13:47 UTC (permalink / raw)
To: Alain Gautherot; +Cc: users
On 23/01/2016 00:11, Alain Gautherot wrote:
> 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.
Yes, it is possible. in your case, you just want to use EAL.
> 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)?
Of course. AFAIK the only requirement for AES-NI is when using AES-NI SW
cryptodev.
It should be disabled in default config.
Sergio
> Thanks,
> Alain
>
> --
> Alain Gautherot
> Edico Genome
> 3344 North Torrey Pines Court, Plaza Level
> La Jolla, CA 92037
> www.edicogenome.com
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-users] Building a DPDK application with librte_malloc only?
2016-01-25 13:47 ` Sergio Gonzalez Monroy
@ 2016-01-25 21:01 ` Alain Gautherot
0 siblings, 0 replies; 3+ messages in thread
From: Alain Gautherot @ 2016-01-25 21:01 UTC (permalink / raw)
To: Sergio Gonzalez Monroy; +Cc: users
Ok sounds good, I figured that EAL logging had a dependency on MEMPOOL+MBUF and was able to skip building of a whole bunch.
Thanks!
Alain
-----Original Message-----
From: Sergio Gonzalez Monroy [mailto:sergio.gonzalez.monroy@intel.com]
Sent: Monday, January 25, 2016 5:48 AM
To: Alain Gautherot <alain@edicogenome.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Building a DPDK application with librte_malloc only?
On 23/01/2016 00:11, Alain Gautherot wrote:
> 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.
Yes, it is possible. in your case, you just want to use EAL.
> 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)?
Of course. AFAIK the only requirement for AES-NI is when using AES-NI SW cryptodev.
It should be disabled in default config.
Sergio
> Thanks,
> Alain
>
> --
> Alain Gautherot
> Edico Genome
> 3344 North Torrey Pines Court, Plaza Level La Jolla, CA 92037
> www.edicogenome.com
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-01-25 21:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-01-23 0:11 [dpdk-users] Building a DPDK application with librte_malloc only? Alain Gautherot
2016-01-25 13:47 ` Sergio Gonzalez Monroy
2016-01-25 21:01 ` Alain Gautherot
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).