From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Polehn, Mike A" <mike.a.polehn@intel.com>, bruce.richardson@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: Prefetch driver variable structure
Date: Tue, 24 Nov 2015 22:26:40 +0100 [thread overview]
Message-ID: <3347211.GiimyAZdiC@xps13> (raw)
In-Reply-To: <745DB4B8861F8E4B9849C970520ABBF14975C429@ORSMSX102.amr.corp.intel.com>
2015-11-11 13:59, Polehn, Mike A:
> Adds ethdev driver prefetch of variable structure to CPU cache 0
> while calling into tx or rx device driver operation.
>
> RFC 2544 test of NIC task test measurement points show improvement
> of lower latency and/or better packet throughput indicating clock
> cycles saved.
>
> Signed-off-by: Mike A. Polehn <mike.a.polehn@intel.com>
There are still some spacing issues with this patch.
Bruce, what is your opinion about this prefetch?
next prev parent reply other threads:[~2015-11-24 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 13:59 Polehn, Mike A
2015-11-24 21:26 ` Thomas Monjalon [this message]
2018-12-19 21:14 ` Ferruh Yigit
-- strict thread matches above, loose matches on Subject: below --
2015-11-10 14:17 Polehn, Mike A
2015-11-10 17:03 ` Stephen Hemminger
2015-11-11 13:56 ` Polehn, Mike A
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=3347211.GiimyAZdiC@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mike.a.polehn@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).