From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by dpdk.org (Postfix) with ESMTP id 0C5FD4BBC for ; Wed, 23 Oct 2013 17:42:57 +0200 (CEST) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id D04F036B57; Wed, 23 Oct 2013 21:13:27 +0530 (IST) Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (Postfix) with ESMTP id B9BA236B32; Wed, 23 Oct 2013 21:13:27 +0530 (IST) Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Wed, 23 Oct 2013 21:13:28 +0530 From: Prashant Upadhyaya To: Jyotiswarup Raiturkar Date: Wed, 23 Oct 2013 21:13:28 +0530 Thread-Topic: [dpdk-dev] query about rte_eal_mp_remote_launch() Thread-Index: Ac7P/HUTSy+DsVv+RH6wK8SuJdPpoAACTwnw Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-TM-AS-MML: No Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] query about rte_eal_mp_remote_launch() X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 15:42:57 -0000 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 p= reclude using pthread_create() calls directly? -Jyoti On Wed, Oct 23, 2013 at 7:46 PM, Prashant Upadhyaya > 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 Beh= alf 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 th= is 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_e= al_mp_remote_launch()? Thanks Jyotiswarup Raiturkar =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D