From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com
Subject: Re: [PATCH 0/4] support AVX2 instruction Rx/Tx function
Date: Sat, 6 Jul 2024 19:51:13 +0100 [thread overview]
Message-ID: <2fa74739-5022-42f7-9084-d8c525a17ad0@amd.com> (raw)
In-Reply-To: <20240619025914.3216054-1-chaoyong.he@corigine.com>
On 6/19/2024 3:59 AM, Chaoyong He wrote:
> This patch series add the support of Rx/Tx function using the
> AVX2 instruction.
>
> Long Wu (4):
> net/nfp: export more interfaces of NFDk
> net/nfp: support AVX2 Tx function
> net/nfp: support AVX2 Rx function
> net/nfp: vector Rx function supports parsing ptype
>
I got some build errors [1], and I can see CI did not run because of
apply error.
Can you please try with local github actions and send a new version?
[1]
- ubuntu-22.04-gcc-static-i386:
Run-time dependency netcope-common found: NO (tried pkgconfig)
drivers/net/nfp/meson.build:56:8: ERROR: Unknown variable
"static_rte_common_nfp".
- ubuntu-22.04-gcc-static-mingw:
drivers/net/nfp/meson.build:56:8: ERROR: Unknown variable
"static_rte_common_nfp".
A full log can be found at
/home/runner/work/dpdk/dpdk/build/meson-logs/meson-log.txt
next prev parent reply other threads:[~2024-07-06 18:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 2:59 Chaoyong He
2024-06-19 2:59 ` [PATCH 1/4] net/nfp: export more interfaces of NFDk Chaoyong He
2024-06-19 2:59 ` [PATCH 2/4] net/nfp: support AVX2 Tx function Chaoyong He
2024-06-19 2:59 ` [PATCH 3/4] net/nfp: support AVX2 Rx function Chaoyong He
2024-06-19 2:59 ` [PATCH 4/4] net/nfp: vector Rx function supports parsing ptype Chaoyong He
2024-07-06 18:51 ` Ferruh Yigit [this message]
2024-07-08 5:52 ` [PATCH 0/4] support AVX2 instruction Rx/Tx function Chaoyong He
2024-07-08 5:58 ` [PATCH v2 " Chaoyong He
2024-07-08 5:58 ` [PATCH v2 1/4] net/nfp: export more interfaces of NFDk Chaoyong He
2024-07-08 5:58 ` [PATCH v2 2/4] net/nfp: support AVX2 Tx function Chaoyong He
2024-07-08 5:58 ` [PATCH v2 3/4] net/nfp: support AVX2 Rx function Chaoyong He
2024-07-08 5:58 ` [PATCH v2 4/4] net/nfp: vector Rx function supports parsing ptype Chaoyong He
2024-07-08 11:45 ` [PATCH v2 0/4] support AVX2 instruction Rx/Tx function Ferruh Yigit
2024-07-09 1:13 ` Chaoyong He
2024-07-09 7:29 ` [PATCH v3 " Chaoyong He
2024-07-09 7:29 ` [PATCH v3 1/4] net/nfp: export more interfaces of NFDk Chaoyong He
2024-07-09 7:29 ` [PATCH v3 2/4] net/nfp: support AVX2 Tx function Chaoyong He
2024-07-09 7:29 ` [PATCH v3 3/4] net/nfp: support AVX2 Rx function Chaoyong He
2024-07-09 7:29 ` [PATCH v3 4/4] net/nfp: vector Rx function supports parsing ptype Chaoyong He
2024-07-09 8:24 ` [PATCH v4 0/5] support AVX2 instruction Rx/Tx function Chaoyong He
2024-07-09 8:24 ` [PATCH v4 1/5] net/nfp: fix compile fail on 32-bit OS Chaoyong He
2024-07-09 8:24 ` [PATCH v4 2/5] net/nfp: export more interfaces of NFDk Chaoyong He
2024-07-09 8:24 ` [PATCH v4 3/5] net/nfp: support AVX2 Tx function Chaoyong He
2024-07-09 8:24 ` [PATCH v4 4/5] net/nfp: support AVX2 Rx function Chaoyong He
2024-07-09 8:24 ` [PATCH v4 5/5] net/nfp: vector Rx function supports parsing ptype Chaoyong He
2024-07-09 13:06 ` [PATCH v4 0/5] support AVX2 instruction Rx/Tx function Ferruh Yigit
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=2fa74739-5022-42f7-9084-d8c525a17ad0@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=oss-drivers@corigine.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).