From: "Yang, Zhiyong" <zhiyong.yang@intel.com>
To: "Wang, Zhihong" <zhihong.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "yuanhan.liu@linux.intel.com" <yuanhan.liu@linux.intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Wang, Zhihong" <zhihong.wang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] config: make AVX and AVX512 configurable
Date: Fri, 28 Apr 2017 02:08:58 +0000 [thread overview]
Message-ID: <E182254E98A5DA4EB1E657AC7CB9BD2A3EBA810E@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <1493334014-69488-1-git-send-email-zhihong.wang@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhihong Wang
> Sent: Friday, April 28, 2017 7:00 AM
> To: dev@dpdk.org
> Cc: yuanhan.liu@linux.intel.com; thomas@monjalon.net; Richardson, Bruce
> <bruce.richardson@intel.com>; Wang, Zhihong <zhihong.wang@intel.com>
> Subject: [dpdk-dev] [PATCH v2] config: make AVX and AVX512 configurable
>
> Making AVX and AVX512 configurable is useful for performance and power
> testing.
>
> The similar kernel patch at https://patchwork.kernel.org/patch/9618883/.
>
> AVX512 support like in rte_memcpy has been in DPDK since 16.04, but it's still
> unproven in rich use cases in hardware. Therefore it's marked as experimental
> for now, will enable it after enough field test and possible optimization.
>
> Signed-off-by: Zhihong Wang <zhihong.wang@intel.com>
> ---
Reviewed-by: Zhiyong Yang <zhiyong.yang@intel.com>
Thanks
Zhiyong
next prev parent reply other threads:[~2017-04-28 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 16:34 [dpdk-dev] [PATCH] " Zhihong Wang
2017-04-27 9:08 ` Thomas Monjalon
2017-04-27 9:18 ` Wang, Zhihong
2017-04-27 9:20 ` Thomas Monjalon
2017-04-27 10:03 ` Wang, Zhihong
2017-04-27 23:00 ` [dpdk-dev] [PATCH v2] " Zhihong Wang
2017-04-28 2:08 ` Yang, Zhiyong [this message]
2017-04-30 21:19 ` Thomas Monjalon
2017-04-28 5:07 ` Yuanhan Liu
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=E182254E98A5DA4EB1E657AC7CB9BD2A3EBA810E@BGSMSX101.gar.corp.intel.com \
--to=zhiyong.yang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yuanhan.liu@linux.intel.com \
--cc=zhihong.wang@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).