From: Bruce Richardson <bruce.richardson@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: jingjing.wu@intel.com, beilei.xing@intel.com, dev@dpdk.org,
helin.zhang@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] net/i40e: add AVX2 Tx function
Date: Wed, 29 Nov 2017 10:02:03 +0000 [thread overview]
Message-ID: <20171129100203.GA2764@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <fa3f2d17-ee8a-6815-0867-a4d257eb9861@intel.com>
On Tue, Nov 28, 2017 at 06:13:35PM -0800, Ferruh Yigit wrote:
> On 11/23/2017 8:53 AM, Bruce Richardson wrote:
> > +ifeq ($(CC_AVX2_SUPPORT), 1)
> > + SRCS-$(CONFIG_RTE_LIBRTE_ACL) += i40e_rxtx_vec_avx2.c
>
> Minor issue:
> s/CONFIG_RTE_LIBRTE_ACL/CONFIG_RTE_LIBRTE_I40E_INC_VECTOR/
>
Ooops. Good catch Ferruh. Hopefully this can be fixed on apply, if not,
or if there are other issues I'll do a V2.
/Bruce
next prev parent reply other threads:[~2017-11-29 10:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 16:53 [dpdk-dev] [PATCH 0/2] AVX2 Vectorized Rx/Tx functions for i40e Bruce Richardson
2017-11-23 16:53 ` [dpdk-dev] [PATCH 1/2] net/i40e: add AVX2 Tx function Bruce Richardson
2017-11-29 2:13 ` Ferruh Yigit
2017-11-29 10:02 ` Bruce Richardson [this message]
2017-11-23 16:53 ` [dpdk-dev] [PATCH 2/2] net/i40e: add AVX2 Rx function Bruce Richardson
2017-11-23 16:56 ` [dpdk-dev] [PATCH 0/2] AVX2 Vectorized Rx/Tx functions for i40e Bruce Richardson
2017-11-27 10:45 ` Zhang, Qi Z
2018-01-09 14:32 ` [dpdk-dev] [PATCH v2 " Bruce Richardson
2018-01-09 14:32 ` [dpdk-dev] [PATCH v2 1/2] net/i40e: add AVX2 Tx function Bruce Richardson
2018-01-09 14:32 ` [dpdk-dev] [PATCH v2 2/2] net/i40e: add AVX2 Rx function Bruce Richardson
2018-01-09 16:30 ` [dpdk-dev] [PATCH v2 0/2] AVX2 Vectorized Rx/Tx functions for i40e John Fastabend
2018-01-10 9:27 ` Richardson, Bruce
2018-01-10 14:25 ` Vincent JARDIN
2018-01-10 14:38 ` Bruce Richardson
2018-01-10 7:11 ` Li, Xiaoyun
2018-01-10 7:14 ` Zhang, Qi Z
2018-01-10 13:49 ` Zhang, Helin
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=20171129100203.GA2764@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@intel.com \
--cc=jingjing.wu@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).