From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
To: Jyotiswarup Raiturkar <jyotisr5@googlemail.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] query about rte_eal_mp_remote_launch()
Date: Wed, 23 Oct 2013 19:46:14 +0530 [thread overview]
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C43EA7059CC@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)
In-Reply-To: <CAJn5u1nHrGSDWM5ApbRRc-nsvL5x7jOd9axx==YvfLdWacbFMw@mail.gmail.com>
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.
===============================================================================
next prev parent reply other threads:[~2013-10-23 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 11:40 Jyotiswarup Raiturkar
2013-10-23 14:16 ` Prashant Upadhyaya [this message]
2013-10-23 14:30 ` Jyotiswarup Raiturkar
2013-10-23 15:43 ` Prashant Upadhyaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C7CE7EEF248E2B48BBA63D0ABEEE700C43EA7059CC@GUREXMB01.ASIAN.AD.ARICENT.COM \
--to=prashant.upadhyaya@aricent.com \
--cc=dev@dpdk.org \
--cc=jyotisr5@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).