From: Stephen Hemminger <stephen@networkplumber.org>
To: Marvin Liu <yong.liu@intel.com>
Cc: bruce.richardson@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] build: enable packet data prefetch
Date: Tue, 22 Sep 2020 07:11:51 -0700 [thread overview]
Message-ID: <20200922071151.2bd35352@hermes.lan> (raw)
In-Reply-To: <20200922082135.62240-1-yong.liu@intel.com>
On Tue, 22 Sep 2020 16:21:35 +0800
Marvin Liu <yong.liu@intel.com> wrote:
> Data prefetch instruction can preload data into cpu’s hierarchical
> cache before data access. Virtualized data paths like virtio utilized
> this feature for acceleration. Since most modern cpus have support
> prefetch function, we can enable packet data prefetch as default.
>
> Signed-off-by: Marvin Liu <yong.liu@intel.com>
>
> diff --git a/config/meson.build b/config/meson.build
> index 69f2aeb605..a0c828a437 100644
> --- a/config/meson.build
> +++ b/config/meson.build
> @@ -109,6 +109,9 @@ if not is_windows
> add_project_link_arguments('-Wl,--no-as-needed', language: 'c')
> endif
>
> +# do prefetch of packet data
> +dpdk_conf.set('RTE_PMD_PACKET_PREFETCH', 1)
> +
> # use pthreads if available for the platform
> if not is_windows
> add_project_link_arguments('-pthread', language: 'c')
With meson, the project has been using rte_config.h for this.
next prev parent reply other threads:[~2020-09-22 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 8:21 Marvin Liu
2020-09-22 14:11 ` Stephen Hemminger [this message]
2020-09-23 2:00 ` Liu, Yong
2020-09-23 1:51 ` [dpdk-dev] [PATCH v2] config: " Marvin Liu
2020-10-14 22:02 ` Thomas Monjalon
2020-10-15 1:21 ` Liu, Yong
2020-10-15 4:09 ` Honnappa Nagarahalli
2020-10-15 8:23 ` Liu, Yong
2020-10-15 9:21 ` Thomas Monjalon
2020-10-15 14:38 ` Honnappa Nagarahalli
2020-11-03 1:57 ` [dpdk-dev] [PATCH v3] drivers/net: enable packet data prefetch on x86 Marvin 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=20200922071151.2bd35352@hermes.lan \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=yong.liu@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).