DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Marvin Liu <yong.liu@intel.com>
Cc: bruce.richardson@intel.com, stephen@networkplumber.org,
	dev@dpdk.org, david.marchand@redhat.com, ferruh.yigit@intel.com,
	maxime.coquelin@redhat.com, honnappa.nagarahalli@arm.com,
	David Christensen <drc@linux.vnet.ibm.com>,
	ruifeng.wang@arm.com
Subject: Re: [dpdk-dev] [PATCH v2] config: enable packet data prefetch
Date: Thu, 15 Oct 2020 00:02:37 +0200	[thread overview]
Message-ID: <3900730.QmOVHUWFXi@thomas> (raw)
In-Reply-To: <20200923015131.101203-1-yong.liu@intel.com>

23/09/2020 03:51, Marvin Liu:
> 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>
> ---
> +#define RTE_PMD_PACKET_PREFETCH 1

We could also remove the related #ifdefs.

What can be the drawback of always enable those prefetches?



  reply	other threads:[~2020-10-14 22:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22  8:21 [dpdk-dev] [PATCH] build: " Marvin Liu
2020-09-22 14:11 ` Stephen Hemminger
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 [this message]
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=3900730.QmOVHUWFXi@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=ferruh.yigit@intel.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stephen@networkplumber.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).