From: ikuzar RABE <ikuzar9295@gmail.com>
To: users@dpdk.org
Cc: halayli@gmail.com
Subject: [dpdk-users] L-threads: is it safe to call pthread_override_set(1) outside of initial_lthread ?
Date: Wed, 15 May 2019 11:45:44 +0200 [thread overview]
Message-ID: <CACNnN_mf2i5OKKZowsR8fywjVoAJ8X46RYT3O5BeKaJ9D-0wmw@mail.gmail.com> (raw)
Hi all,
I am porting legacy code (originally written for a pthread environment) to
run on L-threads.
As a starting point, I took the example here
https://doc.dpdk.org/api/examples_2performance-thread_2pthread_shim_2main_8c-example.html
I 'd like to know if I may call pthread_override_set(1) outside of
initial_thread() :
I intend to initialize mutex and condition variables inside my own
initialization function init_app() directly called from main().
The first call I intend to make inside init_app() is pthread_override_set(1).
is it Ok ?
Thank you for your help,
Regards,
ikuzar
reply other threads:[~2019-05-15 9:45 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_mf2i5OKKZowsR8fywjVoAJ8X46RYT3O5BeKaJ9D-0wmw@mail.gmail.com \
--to=ikuzar9295@gmail.com \
--cc=halayli@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).