From: Rick Jones <rick.jones2@hp.com>
To: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"leitao@linux.vnet.ibm.com" <leitao@linux.vnet.ibm.com>,
"amirv@mellanox.com" <amirv@mellanox.com>,
"yevgenyp@mellanox.co.il" <yevgenyp@mellanox.co.il>,
"klebers@linux.vnet.ibm.com" <klebers@linux.vnet.ibm.com>,
"anton@samba.org" <anton@samba.org>,
"brking@linux.vnet.ibm.com" <brking@linux.vnet.ibm.com>,
"ogerlitz@mellanox.com" <ogerlitz@mellanox.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH] mlx4_en: map entire pages to increase throughput
Date: Mon, 16 Jul 2012 12:42:41 -0700 [thread overview]
Message-ID: <50046EB1.5040909@hp.com> (raw)
In-Reply-To: <20120716190611.GA1023@oc1711230544.ibm.com>
On 07/16/2012 12:06 PM, Thadeu Lima de Souza Cascardo wrote:
> On Mon, Jul 16, 2012 at 10:27:57AM -0700, Rick Jones wrote:
>
>> What is the effect on packet-per-second performance? (eg aggregate,
>> burst-mode netperf TCP_RR with TCP_NODELAY set or perhaps UDP_RR)
>>
> I used uperf with TCP_NODELAY and 16 threads sending from another
> machine 64000-sized writes for 60 seconds.
>
> I get 5898op/s (3.02Gb/s) without the patch against 18022ops/s
> (9.23Gb/s) with the patch.
I was thinking more along the lines of an additional comparison,
explicitly using netperf TCP_RR or something like it, not just the
packets per second from a bulk transfer test.
rick
next prev parent reply other threads:[~2012-07-16 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1342458113-10384-1-git-send-email-cascardo@linux.vnet.ibm.com>
[not found] ` <50044F1D.6000703@hp.com>
2012-07-16 19:06 ` [PATCH] mlx4_en: map entire pages to increase throughput Thadeu Lima de Souza Cascardo
2012-07-16 19:42 ` Rick Jones [this message]
2012-07-16 20:36 ` Or Gerlitz
2012-07-16 20:43 ` Or Gerlitz
2012-07-16 20:57 ` Thadeu Lima de Souza Cascardo
2012-07-18 14:59 ` Or Gerlitz
2012-07-16 20:47 ` Thadeu Lima de Souza Cascardo
2012-07-16 21:08 ` Rick Jones
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=50046EB1.5040909@hp.com \
--to=rick.jones2@hp.com \
--cc=amirv@mellanox.com \
--cc=anton@samba.org \
--cc=brking@linux.vnet.ibm.com \
--cc=cascardo@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=klebers@linux.vnet.ibm.com \
--cc=leitao@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=yevgenyp@mellanox.co.il \
/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).