From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Narcisa Ana Maria Vasile <Narcisa.Vasile@microsoft.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Kadam, Pallavi" <pallavi.kadam@intel.com>,
"Dmitry Malloy (MESHCHANINOV)" <dmitrym@microsoft.com>,
Omar Cardona <ocardona@microsoft.com>,
Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>,
Khoa To <khot@microsoft.com>, Jie Zhou <jizh@microsoft.com>,
Tal Shnaiderman <talshn@nvidia.com>,
"ranjit. menon" <ranjit.menon@intel.com>,
Tyler Retzlaff <roretzla@microsoft.com>
Subject: Re: [dpdk-dev] Importing DATA into the application
Date: Tue, 8 Dec 2020 13:06:13 +0300 [thread overview]
Message-ID: <20201208130613.1fb8d6f8@sovereign> (raw)
In-Reply-To: <3322289.gH0BhIt9ao@thomas>
On Tue, 08 Dec 2020 08:47:15 +0100, Thomas Monjalon wrote:
> 08/12/2020 08:03, Narcisa Ana Maria Vasile:
[...]
> > However, there are a few issues to consider:
> > * We cannot add __declspec(dllimport) when declaring per_lcore__lcore_id for example. We cannot have both __thread and __declspec(dllimport) (can't import thread local variables).
>
> We cannot export a TLS variable? It looks to be a serious issue.
>
>
> > Have you discussed/run into these issues before? Let me know what you think.
>
> Curiously it has never been discussed in 2 years of DPDK porting to Windows.
> Thanks for raising.
Oh, it has been discussed. I've even made a demo about TLS variables in DLLs
with GCC, which supports them, albeit with a penalty, and Clang, which
doesn't support them. At the time, we agreed that having static linking would
be enough as a first step, now we're past it.
prev parent reply other threads:[~2020-12-08 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 7:03 Narcisa Ana Maria Vasile
2020-12-08 7:47 ` Thomas Monjalon
2020-12-08 10:06 ` Dmitry Kozlyuk [this message]
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=20201208130613.1fb8d6f8@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=Harini.Ramakrishnan@microsoft.com \
--cc=Narcisa.Vasile@microsoft.com \
--cc=dev@dpdk.org \
--cc=dmitrym@microsoft.com \
--cc=jizh@microsoft.com \
--cc=khot@microsoft.com \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=roretzla@microsoft.com \
--cc=talshn@nvidia.com \
--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).