From: Ivan Boule <ivan.boule@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org, pablo.de.lara.guarch@intel.com
Subject: Re: [PATCH] app/testpmd: add packet data prefetch in macswap loop
Date: Tue, 3 May 2016 11:50:31 +0200 [thread overview]
Message-ID: <57287467.7080702@6wind.com> (raw)
In-Reply-To: <20160503094516.GC21300@bricha3-MOBL3>
On 05/03/2016 11:45 AM, Bruce Richardson wrote:
> On Mon, May 02, 2016 at 05:29:37PM +0530, Jerin Jacob wrote:
>> prefetch the next packet data address in advance in macswap loop
>> for performance improvement.
>>
>> ...
>> for (i = 0; i < nb_rx; i++) {
>> + if (likely(i < nb_rx - 1))
>> + rte_prefetch0(rte_pktmbuf_mtod(pkts_burst[i + 1],
>> + void *));
>
> At least on IA platforms, there is no issue with prefetching beyond the end of
> the array, since it's only a hint to the cpu. If this is true for other platforms,
> then I suggest we just drop the conditional and just always prefetch.
This is an interesting point.
Bruce, are you suggesting that prefetching at an invalid [virtual]
address won't trigger a CPU exception?
Ivan
>
> /Bruce
>
>> mb = pkts_burst[i];
>> eth_hdr = rte_pktmbuf_mtod(mb, struct ether_hdr *);
next prev parent reply other threads:[~2016-05-03 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 11:59 [PATCH] app/testpmd: add packet data prefetch in macswap loop Jerin Jacob
2016-05-02 17:48 ` De Lara Guarch, Pablo
2016-05-03 12:46 ` Jerin Jacob
2016-05-03 9:45 ` Bruce Richardson
2016-05-03 9:48 ` De Lara Guarch, Pablo
2016-05-03 10:16 ` Bruce Richardson
2016-05-03 9:50 ` Ivan Boule [this message]
2016-05-03 10:20 ` Bruce Richardson
2016-05-10 12:26 ` Ananyev, Konstantin
2016-05-03 14:07 ` [PATCH v2] app/testpmd: add packet data pointer prefetch in the forwarding loop Jerin Jacob
2016-05-03 14:33 ` Thomas Monjalon
2016-06-07 11:19 ` De Lara Guarch, Pablo
2016-06-08 15:57 ` 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=57287467.7080702@6wind.com \
--to=ivan.boule@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=pablo.de.lara.guarch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.