From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: Tarun Badnora <tarun.badnora@clear-trail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Anurag Berdia <anurag.berdia@clear-trail.com>,
Omar Cardona <ocardona@microsoft.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Daniel Havey <dahavey@microsoft.com>,
Tyler Retzlaff <roretzla@microsoft.com>
Subject: RE: DPDK for Windows with MSVC compiler
Date: Fri, 25 Mar 2022 13:25:51 +0000 [thread overview]
Message-ID: <BL1PR12MB5945578F10D3681FEDF43240B91A9@BL1PR12MB5945.namprd12.prod.outlook.com> (raw)
In-Reply-To: <PN1PR0101MB1901E81B3277F2041347CF49A4189@PN1PR0101MB1901.INDPRD01.PROD.OUTLOOK.COM>
> Is there a way to integrate DPDK module, built with clang/mingw, to our
> MSVC application ?
> I know both are different compilers, but in case if you are aware of a
> way/tweak that will be of our help.
> OR
> If porting our application is the only option available then which
> compiler (clang or mingw) is recommended for optimal performance.
DPDK headers are incompatible with MSVC
due to heavy use of extensions common to GCC, clang, and ICC.
DPDK libraries can be linked trivially.
If your app cannot be easily recompiled with clang,
I think the best way is to use two compilers:
compile the module that interfaces DPDK with clang
and the rest of the app with MSVC,
link DPDK libraries as any other external libraries.
Note that DPDK installation on Windows is not fully functional yet:
it does not install pthread.h which you can find in lib/eal/windows/include.
+Tyler who might have relevant experience.
next prev parent reply other threads:[~2022-03-25 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 10:26 Tarun Badnora
2022-03-22 11:55 ` Dmitry Kozlyuk
2022-03-23 8:30 ` Tarun Badnora
2022-03-25 13:25 ` Dmitry Kozlyuk [this message]
2022-03-25 16:35 ` Tyler Retzlaff
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=BL1PR12MB5945578F10D3681FEDF43240B91A9@BL1PR12MB5945.namprd12.prod.outlook.com \
--to=dkozlyuk@nvidia.com \
--cc=anurag.berdia@clear-trail.com \
--cc=dahavey@microsoft.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=ocardona@microsoft.com \
--cc=roretzla@microsoft.com \
--cc=tarun.badnora@clear-trail.com \
/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).