From: Rick Jones <rick.jones2@hp.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>,
Tom Herbert <therbert@google.com>,
netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [RFC][PATCH 0/5] RFS hardware acceleration (v2)
Date: Fri, 19 Nov 2010 13:16:46 -0800 [thread overview]
Message-ID: <4CE6E93E.7000901@hp.com> (raw)
In-Reply-To: <1290194386.2671.59.camel@bwh-desktop>
Ben Hutchings wrote:
> So, some preliminary benchmark results.
>
> Tom said he was using 200 concurrent netperf TCP_RR tests, so I've done
> the same, using netperf 2.4.1 (a bit out of date, I know).
Not a huge deal for a basic TCP_RR test though.
<data snipped>
> So accelerated RFS gave a 6-13% improvement over software RFS in
> transaction rate for these various cases.
Do you have any data on frequency with which unpinned netperf processes migrated
from one core to another? Or PCIe utilization?
rick jones
prev parent reply other threads:[~2010-11-19 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 18:42 [RFC][PATCH 0/5] RFS hardware acceleration (v2) Ben Hutchings
2010-11-19 18:44 ` [RFC][PATCH 1/5] genirq: Add IRQ affinity notifiers Ben Hutchings
2010-11-19 18:44 ` [RFC][PATCH 2/5] lib: cpu_rmap: CPU affinity reverse-mapping Ben Hutchings
2010-11-19 18:47 ` [RFC][PATCH 3/5] net: RPS: Enable hardware acceleration Ben Hutchings
2010-11-19 18:47 ` [RFC][PATCH 4/5] sfc: Limit filter search depth further for performance hints (i.e. RFS) Ben Hutchings
2010-11-19 18:48 ` [RFC][PATCH 5/5] sfc: Implement RFS acceleration Ben Hutchings
2010-11-19 19:19 ` [RFC][PATCH 0/5] RFS hardware acceleration (v2) Ben Hutchings
2010-11-19 19:42 ` Tom Herbert
2010-11-19 21:16 ` Rick Jones [this message]
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=4CE6E93E.7000901@hp.com \
--to=rick.jones2@hp.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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).