[dpdk-dev] query about rte_eal_mp_remote_launch()

[dpdk-dev] query about rte_eal_mp_remote_launch()

[Jyotiswarup Raiturkar]

Hello Devs
I'm new to DPDK and trying to understand the basics..
I want to write a DPDK app where I want to configure shm rings on the fly,
and I want one thread(per core) to service the ring.
In some of the examples I saw rte_eal_mp_remote_launch() being used, but
this is a one time launch. Can I use pthread_create() on-the-fly (taking
care of CPU core allocation), after doing an initial threads launch using
rte_eal_mp_remote_launch()?
 Thanks
Jyotiswarup Raiturkar

Re: [dpdk-dev] query about rte_eal_mp_remote_launch()

[Prashant Upadhyaya]

Hi Jyoti,

You must carefully analyse your usecase.
Typically each core must run a tight loop (and therefore one thread spawned by remote launch) which does a while 1 { get packet, service packet }
You should try to build your application around the above paradigm.

One of your cores can service the slow path using traditional linux with a tap interface.

Regards
-Prashant


-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jyotiswarup Raiturkar
Sent: Wednesday, October 23, 2013 5:11 PM
To: dev@dpdk.org
Subject: [dpdk-dev] query about rte_eal_mp_remote_launch()

Hello Devs
I'm new to DPDK and trying to understand the basics..
I want to write a DPDK app where I want to configure shm rings on the fly, and I want one thread(per core) to service the ring.
In some of the examples I saw rte_eal_mp_remote_launch() being used, but this is a one time launch. Can I use pthread_create() on-the-fly (taking care of CPU core allocation), after doing an initial threads launch using rte_eal_mp_remote_launch()?
 Thanks
Jyotiswarup Raiturkar




===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================

Re: [dpdk-dev] query about rte_eal_mp_remote_launch()

[Jyotiswarup Raiturkar]

Hi Prashant

Thanks for the reply.

I understand what you said. But my query was can i use pthread_create() to
create the 'tight loop' threads on demand, rather than spawing the threads
at start with rte_eal_mp_remote_launch().  Does anything in the dpdk core
preclude using pthread_create() calls directly?

-Jyoti




On Wed, Oct 23, 2013 at 7:46 PM, Prashant Upadhyaya <
prashant.upadhyaya@aricent.com> wrote:

> Hi Jyoti,
>
> You must carefully analyse your usecase.
> Typically each core must run a tight loop (and therefore one thread
> spawned by remote launch) which does a while 1 { get packet, service packet
> }
> You should try to build your application around the above paradigm.
>
> One of your cores can service the slow path using traditional linux with a
> tap interface.
>
> Regards
> -Prashant
>
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jyotiswarup Raiturkar
> Sent: Wednesday, October 23, 2013 5:11 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] query about rte_eal_mp_remote_launch()
>
> Hello Devs
> I'm new to DPDK and trying to understand the basics..
> I want to write a DPDK app where I want to configure shm rings on the fly,
> and I want one thread(per core) to service the ring.
> In some of the examples I saw rte_eal_mp_remote_launch() being used, but
> this is a one time launch. Can I use pthread_create() on-the-fly (taking
> care of CPU core allocation), after doing an initial threads launch using
> rte_eal_mp_remote_launch()?
>  Thanks
> Jyotiswarup Raiturkar
>
>
>
>
>
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
>
> ===============================================================================
>

Re: [dpdk-dev] query about rte_eal_mp_remote_launch()

[Prashant Upadhyaya]

Hi,

So far as you are doing the init properly in a controlled fashion from one core, you should be able to orchestrate the usecase with your own threads.
I don't think so there should be any limitations.

Regards
-Prashant


From: Jyotiswarup Raiturkar [mailto:jyotisr5@googlemail.com]
Sent: Wednesday, October 23, 2013 8:01 PM
To: Prashant Upadhyaya
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] query about rte_eal_mp_remote_launch()

Hi Prashant

Thanks for the reply.

I understand what you said. But my query was can i use pthread_create() to create the 'tight loop' threads on demand, rather than spawing the threads at start with rte_eal_mp_remote_launch().  Does anything in the dpdk core preclude using pthread_create() calls directly?

-Jyoti



On Wed, Oct 23, 2013 at 7:46 PM, Prashant Upadhyaya <prashant.upadhyaya@aricent.com<mailto:prashant.upadhyaya@aricent.com>> wrote:
Hi Jyoti,

You must carefully analyse your usecase.
Typically each core must run a tight loop (and therefore one thread spawned by remote launch) which does a while 1 { get packet, service packet }
You should try to build your application around the above paradigm.

One of your cores can service the slow path using traditional linux with a tap interface.

Regards
-Prashant


-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org<mailto:dev-bounces@dpdk.org>] On Behalf Of Jyotiswarup Raiturkar
Sent: Wednesday, October 23, 2013 5:11 PM
To: dev@dpdk.org<mailto:dev@dpdk.org>
Subject: [dpdk-dev] query about rte_eal_mp_remote_launch()

Hello Devs
I'm new to DPDK and trying to understand the basics..
I want to write a DPDK app where I want to configure shm rings on the fly, and I want one thread(per core) to service the ring.
In some of the examples I saw rte_eal_mp_remote_launch() being used, but this is a one time launch. Can I use pthread_create() on-the-fly (taking care of CPU core allocation), after doing an initial threads launch using rte_eal_mp_remote_launch()?
 Thanks
Jyotiswarup Raiturkar



===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================





===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================