From: "Wiles, Keith" <keith.wiles@intel.com>
To: David Aldrich <David.Aldrich@EMEA.NEC.COM>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Is DPDK compatible with C++11 threads?
Date: Tue, 8 Nov 2016 17:04:45 +0000 [thread overview]
Message-ID: <B1082639-11F2-413E-B414-1F0C1A6E7867@intel.com> (raw)
In-Reply-To: <c245ea7b4d224ead900ea371094482a6@EUX13SRV1.EU.NEC.COM>
> On Nov 8, 2016, at 5:12 AM, David Aldrich <David.Aldrich@EMEA.NEC.COM> wrote:
>
> Hi
>
> As a beginner with DPDK, I want to consider how we can convert an existing Linux application from using the kernel network stack to using DPDK.
>
> This existing app is multi-threaded, using the C++11 thread, mutex etc. classes. We assign threads to cores by calling pthread_setaffinity_np().
>
> I have looked at the DPDK helloworld application and see that it launches threads using the DPDK API:
>
> /* call lcore_hello() on every slave lcore */
> RTE_LCORE_FOREACH_SLAVE(lcore_id) {
> rte_eal_remote_launch(lcore_hello, NULL, lcore_id);
> }
>
> If we use DPDK, can we retain our existing C++11 threads or are we obliged to use the DPDK threading APIs exclusively?
You should be able to use the standard C++11 threads I believe, in DPDK we are just using pthreads and set affinity to lock a thread to a core. You can still use pthreads in your application.
>
> Perhaps a more basic question is applicable: is DPDK compatible with C++?
I believe building DPDK with C++ code does work, but I have not tried it myself.
>
> Best regards
>
> David
>
>
>
> Best regards
>
> David
>
Regards,
Keith
next prev parent reply other threads:[~2016-11-08 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 13:12 David Aldrich
2016-11-08 17:04 ` Wiles, Keith [this message]
2016-11-08 17:23 ` Pavey, Nicholas
2016-11-09 8:40 ` David Aldrich
2016-11-09 21:00 ` Wiles, Keith
2016-11-10 4:14 ` Anupam Kapoor
2016-11-10 12:49 ` Pavey, Nicholas
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=B1082639-11F2-413E-B414-1F0C1A6E7867@intel.com \
--to=keith.wiles@intel.com \
--cc=David.Aldrich@EMEA.NEC.COM \
--cc=users@dpdk.org \
/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).