From: "Jan Viktorin" <viktorin@rehivetech.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] eal: introduce rte_prefetch_non_temporal
Date: Thu, 11 Feb 2016 12:43:38 +0100 [thread overview]
Message-ID: <20160211124338.19f6154b@pcviktorin.fit.vutbr.cz> (raw)
In-Reply-To: <1449415470-25545-2-git-send-email-jerin.jacob@caviumnetworks.com>
I am OK with this patch.
On Sun, 6 Dec 2015 20:54:29 +0530
Jerin Jacob <jerin.jacob@caviumnetworks.com> wrote:
> non-temporal/transient/stream version of rte_prefetch0()
>
> The non-temporal prefetch is intended as a prefetch hint that processor
> will use the prefetched data only once or short period,
> unlike the rte_prefetch0() function which imply that
> prefetched data to use repeatedly.
>
> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Acked-by: Jan Viktorin <viktorin@rehivetech.com>
next prev parent reply other threads:[~2016-02-11 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 15:24 [dpdk-dev] [RFC PATCH 0/2] Fix examples/distributor build issue for non x86 Jerin Jacob
2015-12-06 15:24 ` [dpdk-dev] [PATCH 1/2] eal: introduce rte_prefetch_non_temporal Jerin Jacob
2016-02-11 11:00 ` Thomas Monjalon
2016-02-11 11:43 ` Jan Viktorin [this message]
2015-12-06 15:24 ` [dpdk-dev] [PATCH 2/2] examples/distributor: remove IA specific __mm_prefetch Jerin Jacob
2016-01-29 3:21 ` [dpdk-dev] [RFC PATCH 0/2] Fix examples/distributor build issue for non x86 Jerin Jacob
2016-01-29 15:03 ` Bruce Richardson
2016-01-29 16:53 ` Jerin Jacob
2016-02-12 11:13 ` [dpdk-dev] [PATCH v2 " Jerin Jacob
2016-02-12 11:13 ` [dpdk-dev] [PATCH v2 1/2] eal: introduce rte_prefetch_non_temporal Jerin Jacob
2016-02-12 11:13 ` [dpdk-dev] [PATCH v2 2/2] examples/distributor: remove IA specific __mm_prefetch Jerin Jacob
2016-02-16 6:28 ` [dpdk-dev] [PATCH v2 0/2] Fix examples/distributor build issue for non x86 Thomas Monjalon
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=20160211124338.19f6154b@pcviktorin.fit.vutbr.cz \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.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).