From: ikuzar RABE <ikuzar9295@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] how to migrate from pthread to L-thread
Date: Mon, 25 Mar 2019 16:58:58 +0100 [thread overview]
Message-ID: <CACNnN_kuMD1TFu1LONUV=m6m0VzyLv8w6zS3+q=jxRu4KDgyig@mail.gmail.com> (raw)
Hello all,
I work on Linux (Debian 8), DPDK v18.05.1
I work on legacy code which reads packets from NIC's ports using several
readers (using libpcap and threads from pthread API).
The aim is to remove libpcap and migrate to DPDK using L-thread (
https://doc.dpdk.org/guides-16.04/sample_app_ug/performance_thread.html)
Is it possible to directly call L-thread functions (lthread_create,
lthread_mutex_lock, etc.) instead of using pthread shim ?
(
https://github.com/Juniper/contrail-dpdk/blob/master/examples/performance-thread/pthread_shim/pthread_shim.h
)
What are the advantages/drawbacks of using pthread shim / lthread API?
With pthread shim, I do not know where to call pthread_override_set(1) and
pthread_override_set(0), that's why I 'd like to directly call L-thread
functions.
In the following example (see link below), it is simple because there is no
interraction between threads running on different lcores.
https://doc.dpdk.org/api/examples_2performance-thread_2pthread_shim_2main_8c-example.html
Regards,
ikuzar
reply other threads:[~2019-03-25 15:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CACNnN_kuMD1TFu1LONUV=m6m0VzyLv8w6zS3+q=jxRu4KDgyig@mail.gmail.com' \
--to=ikuzar9295@gmail.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).