From: Isaac Boukris <iboukris@gmail.com>
To: fengchengwen <fengchengwen@huawei.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org,
"haijie1@huawei.com >> Jie Hai" <haijie1@huawei.com>,
huangdengdui@huawei.com
Subject: Re: Use of strtok() in dpdk code
Date: Tue, 22 Oct 2024 15:27:05 +0300 [thread overview]
Message-ID: <CAC-fF8SLCCqRM8qpeg321XO16pe9ge7sm3Zz3rUuw7WrXdrMzQ@mail.gmail.com> (raw)
In-Reply-To: <282a31cf-7ccd-4de3-99b9-687287b20e24@huawei.com>
Hi
On Tue, Oct 22, 2024 at 9:51 AM fengchengwen <fengchengwen@huawei.com> wrote:
>
> DPDK is just a SDK, it's not an application (although DPDK provided simple examples).
> Many code will developped based on DPDK, we can't predict how it was implemented.
> So there maybe a DPDK thread and a application thread both invoke strtok().
I think even dpdk threads such as the telemetry ones might invoke (the
same) strtok() at the same time.
> From this point of view, I hope that DPDK solves some of the reentrant problems of
> such C functions (e.g. strtok()\strerror()).
>
> Actually, we've try to solve before, but unfortunately it wasn't merged.
> 1\ strtok(): https://inbox.dpdk.org/dev/20231114110006.91148-1-haijie1@huawei.com/T/#u
> 2\ strerror(): https://inbox.dpdk.org/dev/20231114123552.398072-1-huangdengdui@huawei.com/T/#u
+1
next prev parent reply other threads:[~2024-10-22 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 18:30 Isaac Boukris
2024-10-22 1:08 ` Stephen Hemminger
2024-10-22 6:51 ` fengchengwen
2024-10-22 12:27 ` Isaac Boukris [this message]
2024-10-22 15:25 ` Stephen Hemminger
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=CAC-fF8SLCCqRM8qpeg321XO16pe9ge7sm3Zz3rUuw7WrXdrMzQ@mail.gmail.com \
--to=iboukris@gmail.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=haijie1@huawei.com \
--cc=huangdengdui@huawei.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).