[dpdk-dev] Using DPDK in a multiprocess environment

2014-04-10 Thread Etai Lev Ran
ess is required. The reason is simple, if > >>process A thinks the virtual address of an mbuf is 123, and process > >>B thinks the virtual address of the same mbuf is 456, either > >>process may segmentation fault, accessing mbuf memory that is not > >>actua

[dpdk-dev] Using DPDK in a multiprocess environment

2014-04-09 Thread Richardson, Bruce
mapped properly. /Bruce > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Rogers, Gerald > Sent: Tuesday, April 08, 2014 6:00 PM > To: elevran; Shaw, Jeffrey B > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] Using DPDK in a multiprocess env

[dpdk-dev] Using DPDK in a multiprocess environment

2014-04-08 Thread elevran
gt; From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Etai Lev Ran > Sent: Tuesday, April 08, 2014 8:13 AM > To: dev at dpdk.org > Subject: [dpdk-dev] Using DPDK in a multiprocess environment > > Hi, > > > > I'd like to split DPDK application functionality in

[dpdk-dev] Using DPDK in a multiprocess environment

2014-04-08 Thread Etai Lev Ran
Hi, I'd like to split DPDK application functionality into a setup (primary) process and business logic (secondary) processes. The secondary processes access the hardware queues directly (exclusive queue per process) and not through software rings. I'm running into an initialization problem:

[dpdk-dev] Using DPDK in a multiprocess environment

2014-04-08 Thread Rogers, Gerald
;> Jeff >> >> -Original Message----- >> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Etai Lev Ran >> Sent: Tuesday, April 08, 2014 8:13 AM >> To: dev at dpdk.org >> Subject: [dpdk-dev] Using DPDK in a multiprocess environment >> >> Hi,

[dpdk-dev] Using DPDK in a multiprocess environment

2014-04-08 Thread Shaw, Jeffrey B
To: dev at dpdk.org Subject: [dpdk-dev] Using DPDK in a multiprocess environment Hi, I'd like to split DPDK application functionality into a setup (primary) process and business logic (secondary) processes. The secondary processes access the hardware queues directly (exclusive queue p