From: Tal Shnaiderman <talshn@nvidia.com>
To: Ali Alnubani <alialnu@nvidia.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Odi Assli <odia@nvidia.com>, "Rong, Leyi" <leyi.rong@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Kadam, Pallavi" <pallavi.kadam@intel.com>,
"Menon, Ranjit" <ranjit.menon@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Raslan Darawsheh <rasland@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/3] AVX512 vPMD on i40e
Date: Wed, 20 Jan 2021 06:25:53 +0000 [thread overview]
Message-ID: <DM6PR12MB3945A6FE02C47F856D48415BA4A20@DM6PR12MB3945.namprd12.prod.outlook.com> (raw)
In-Reply-To: <MWHPR12MB1472B0956ACDAACA877DF050DAA30@MWHPR12MB1472.namprd12.prod.outlook.com>
> Subject: RE: [PATCH v3 0/3] AVX512 vPMD on i40e
>
> Hi,
>
> > > Hi Guys,
> > >
> > > I tested it in my side and it works
> >
> > Thanks Assli, Leyi, I will proceed with the patch.
> >
> > > Can you please the Bugzilla bug 619?
> > >
>
> The patch "add AVX512 vector path" also caused a build failure when cross
> compiling on Linux using mingw, and it's still reproducing in next-net
> (517969c95).
>
> ```
> $ meson --werror --buildtype=debugoptimized --cross-file config/x86/cross-
> mingw -Dexamples=helloworld build && ninja-build -C build -j32
>
> [221/232] Generating symbol file lib/librte_mbuf-21.dll.p/librte_mbuf-
> 21.dll.symbols
> [222/232] Generating symbol file lib/librte_hash-21.dll.p/librte_hash-
> 21.dll.symbols
> [223/232] Linking target lib/librte_net-21.dll [224/232] Compiling C object
> drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.obj
> FAILED: drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.obj
> ...
> drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.obj.d -o
> drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.obj -c
> ../../root/dpdk/drivers/net/i40e/i40e_rxtx_vec_avx512.c
> {standard input}: Assembler messages:
> {standard input}:112: Error: invalid register for .seh_savexmm {standard
> input}:114: Error: invalid register for .seh_savexmm ...
> ...
> {standard input}:25351: Error: invalid register for .seh_savexmm {standard
> input}:25352: Error: invalid register for .seh_savexmm [225/232] Generating
> symbol file lib/librte_net-21.dll.p/librte_net-21.dll.symbols
> ninja: build stopped: subcommand failed.
> ```
>
> OS: Fedora 32
> Meson: 0.55.3
> MinGW: Fedora MinGW 9.2.1-6.fc32
>
> - Ali
Those errors were detected in the CI tests for this patch [1], we should pay more attention to those now that 2 PMDs are supported on Windows.
[1]: https://lab.dpdk.org/results/dashboard/patchsets/15164/
next prev parent reply other threads:[~2021-01-20 6:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 2:19 [dpdk-dev] [PATCH " Leyi Rong
2020-12-15 2:19 ` [dpdk-dev] [PATCH 1/3] net/i40e: remove devarg use-latest-supported-vec Leyi Rong
2020-12-15 2:19 ` [dpdk-dev] [PATCH 2/3] net/i40e: add AVX512 vector path Leyi Rong
2020-12-15 2:19 ` [dpdk-dev] [PATCH 3/3] net/i40e: optimize Tx by using AVX512 Leyi Rong
2021-01-07 7:44 ` [dpdk-dev] [PATCH v2 0/3] AVX512 vPMD on i40e Leyi Rong
2021-01-07 7:44 ` [dpdk-dev] [PATCH v2 1/3] net/i40e: remove devarg use-latest-supported-vec Leyi Rong
2021-01-13 6:12 ` Lu, Wenzhuo
2021-01-13 13:40 ` Ferruh Yigit
2021-01-07 7:44 ` [dpdk-dev] [PATCH v2 2/3] net/i40e: add AVX512 vector path Leyi Rong
2021-01-13 6:13 ` Lu, Wenzhuo
2021-01-07 7:44 ` [dpdk-dev] [PATCH v2 3/3] net/i40e: optimize Tx by using AVX512 Leyi Rong
2021-01-13 6:12 ` Lu, Wenzhuo
2021-01-13 9:53 ` [dpdk-dev] [PATCH v2 0/3] AVX512 vPMD on i40e Zhang, Qi Z
2021-01-14 6:39 ` [dpdk-dev] [PATCH v3 " Leyi Rong
2021-01-14 6:39 ` [dpdk-dev] [PATCH v3 1/3] net/i40e: remove devarg use-latest-supported-vec Leyi Rong
2021-01-15 13:36 ` Ferruh Yigit
2021-01-14 6:39 ` [dpdk-dev] [PATCH v3 2/3] net/i40e: add AVX512 vector path Leyi Rong
2021-01-14 6:39 ` [dpdk-dev] [PATCH v3 3/3] net/i40e: optimize Tx by using AVX512 Leyi Rong
2021-01-14 7:37 ` [dpdk-dev] [PATCH v3 0/3] AVX512 vPMD on i40e Zhang, Qi Z
2021-01-17 11:26 ` Odi Assli
2021-01-18 13:58 ` Rong, Leyi
2021-01-18 14:24 ` Ferruh Yigit
2021-01-18 14:53 ` Odi Assli
2021-01-18 16:36 ` Ferruh Yigit
2021-01-19 13:46 ` Ali Alnubani
2021-01-20 6:25 ` Tal Shnaiderman [this message]
2021-01-20 8:36 ` David Marchand
2021-01-20 9:18 ` Ferruh Yigit
2021-01-20 9:23 ` Thomas Monjalon
2021-01-20 9:53 ` David Marchand
2021-01-20 10:05 ` Ali Alnubani
2021-01-20 17:51 ` Ferruh Yigit
2021-01-20 18:04 ` Ferruh Yigit
2021-01-21 5:01 ` Kadam, Pallavi
2021-01-25 14:35 ` David Marchand
2021-01-26 16:17 ` Rong, Leyi
2021-01-26 16:22 ` Thomas Monjalon
2021-01-26 16:39 ` Ferruh Yigit
2021-01-26 16:48 ` Thomas Monjalon
2021-01-26 16:51 ` Ferruh Yigit
2021-01-28 20:35 ` Dmitry Kozlyuk
2021-01-28 21:24 ` Thomas Monjalon
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=DM6PR12MB3945A6FE02C47F856D48415BA4A20@DM6PR12MB3945.namprd12.prod.outlook.com \
--to=talshn@nvidia.com \
--cc=alialnu@nvidia.com \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=leyi.rong@intel.com \
--cc=odia@nvidia.com \
--cc=pallavi.kadam@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=ranjit.menon@intel.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@intel.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).