From: Eric Dumazet <edumazet@google.com>
To: panxinhui <xinhui@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, Kevin Hao <haokexin@gmail.com>,
Torsten Duwe <duwe@suse.de>,
Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
Subject: Re: [RFC] implement QUEUED spinlocks on powerpc
Date: Mon, 6 Feb 2017 22:46:10 -0800 [thread overview]
Message-ID: <CANn89iJKKc80MO2Ysz_c-_-XerUUk01Fe5Pn59r7zRTUMtpZfA@mail.gmail.com> (raw)
In-Reply-To: <4206026c-f659-d690-b6b2-31d1cedf55cb@linux.vnet.ibm.com>
On Mon, Feb 6, 2017 at 10:21 PM, panxinhui <xinhui@linux.vnet.ibm.com> wrote:
> hi all
> I do some netperf tests and get some benchmark results.
> I also attach my test script and netperf-result(Excel)
>
> There are two machine. one runs netserver and the other runs netperf
> benchmark. 1000Mbps network is connected with them.
>
> #ip link infomation
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
> UNKNOWN mode DEFAULT group default qlen 1000
> link/ether ba:68:9c:14:32:02 brd ff:ff:ff:ff:ff:ff
>
> According to the results, there is not much performance gap with each other.
> And as we are only testing the throughput, the pvqspinlock shows the
> overhead of its pv stuff. but qspinlock shows a little improvement than
> spinlock. My simple summary in this testcase is
> qspinlock > spinlock > pvqspinlock.
>
> when run 200 concurrent netperf, I paste the total throughput here.
>
> concurrent runners| total throughput | variance
> -------------------------------------------
> spinlock | 199 | 66882.8 | 89.93
> -------------------------------------------
> qspinlock | 199 | 66350.4 | 72.0239
> -------------------------------------------
> pvqspinlock | 199 | 64740.5 | 85.7837
>
> You could see more data in nerperf.xlsx
>
> thanks
> xinhui
Hi xinhui
1Gbit NIC is too slow for this use case. I would try a 10Gbit NIC at least...
Alternatively, you could use loopback interface. (netperf -H 127.0.0.1)
tc qd add dev lo root pfifo limit 10000
next prev parent reply other threads:[~2017-02-07 6:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 17:05 [RFC] implement QUEUED spinlocks on powerpc Eric Dumazet
2017-02-01 20:37 ` Benjamin Herrenschmidt
2017-02-02 4:04 ` Michael Ellerman
2017-02-02 4:40 ` Eric Dumazet
2017-02-02 4:42 ` Benjamin Herrenschmidt
2017-02-07 6:21 ` panxinhui
2017-02-07 6:46 ` Eric Dumazet [this message]
2017-02-07 7:22 ` panxinhui
2017-02-13 9:08 ` panxinhui
2017-02-15 10:17 ` panxinhui
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=CANn89iJKKc80MO2Ysz_c-_-XerUUk01Fe5Pn59r7zRTUMtpZfA@mail.gmail.com \
--to=edumazet@google.com \
--cc=benh@kernel.crashing.org \
--cc=duwe@suse.de \
--cc=eric.dumazet@gmail.com \
--cc=haokexin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=xinhui.pan@linux.vnet.ibm.com \
--cc=xinhui@linux.vnet.ibm.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).