[dpdk-dev] Decoupling DPDK from EAL

our thread API to accommodate DPDK thread model). > > Fran?ois-Fr?d?ric > > >> -Message d'origine- >> De : Jason Vassbender [mailto:jason.vassbender at gmail.com] >> Envoy? : mercredi 4 d?cembre 2013 10:25 >> ? : Fran?ois-Fr?d?ric Ozog >> Cc : dev at

[dpdk-dev] Decoupling DPDK from EAL

: mercredi 4 d?cembre 2013 10:25 > ??: Fran?ois-Fr?d?ric Ozog > Cc?: dev at dpdk.org > Objet?: Re: [dpdk-dev] Decoupling DPDK from EAL > > Hey, > > I guess the main hurdle is that we already have our own multi-threaded > architecture and ways to control thread startup/s

[dpdk-dev] Decoupling DPDK from EAL

d a critical point, so, what is the > specific major hurdle you see in the integration? > > Fran?ois-Fr?d?ric > > >> -Message d'origine- >> De : dev [mailto:dev-bounces at dpdk.org] De la part de Jason Vassbender >> Envoy? : mardi 3 d?cembre 2013 22:51 >

[dpdk-dev] Decoupling DPDK from EAL

; ??: dev at dpdk.org > Objet?: [dpdk-dev] Decoupling DPDK from EAL > > 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

[dpdk-dev] Decoupling DPDK from EAL

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 an