linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: panxinhui <xinhui@linux.vnet.ibm.com>
To: Eric Dumazet <edumazet@google.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: Wed, 15 Feb 2017 18:17:26 +0800	[thread overview]
Message-ID: <7b84eafd-b15a-c5b3-d94c-fcef95b6de50@linux.vnet.ibm.com> (raw)
In-Reply-To: <6e17ab77-4987-610b-7827-d6c6fb1791c0@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 2418 bytes --]



在 2017/2/13 下午5:08, panxinhui 写道:
> 
> 
> 在 2017/2/7 下午2:46, Eric Dumazet 写道:
>> 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)
>>>
> HI, all
> I use loopback interface to run netperf tests,
> #tc qd add dev lo root pfifo limit 10000
> #ip link
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc pfifo state UNKNOWN mode DEFAULT group default qlen 1000
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 
> and put the result in netperf.xlsx(excel)
> 
> It is a 32 vcpus P8 machine, with 32Gib memory.
> 
> This time spinlock is the best one, qspinlock > pvqspinlock. So sad.
> 
This time, I have appiled some optimising patches on pvqspinlock.
When there is a high contention, the performance has a good improvement ans is very similar to spinlock.

Result is attached in netperf.xlsx

thanks
xinhui

> thanks
> xinhui
>>> 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
>>

[-- Attachment #2: netperf.xlsx --]
[-- Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, Size: 72195 bytes --]

      reply	other threads:[~2017-02-15 10:17 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
2017-02-07  7:22           ` panxinhui
2017-02-13  9:08           ` panxinhui
2017-02-15 10:17             ` panxinhui [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=7b84eafd-b15a-c5b3-d94c-fcef95b6de50@linux.vnet.ibm.com \
    --to=xinhui@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=duwe@suse.de \
    --cc=edumazet@google.com \
    --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 \
    /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).