From: Will Deacon <will.deacon@arm.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
benh@kernel.crashing.org, paulmck@linux.vnet.ibm.com,
Ingo Molnar <mingo@elte.hu>, Boqun Feng <boqun.feng@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
1vier1@web.de, Davidlohr Bueso <dave@stgolabs.net>,
Pablo Neira Ayuso <pablo@netfilter.org>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 8/7] net/netfilter/nf_conntrack_core: Remove another memory barrier
Date: Tue, 6 Sep 2016 18:56:48 +0100 [thread overview]
Message-ID: <20160906175648.GC29382@arm.com> (raw)
In-Reply-To: <5d88110f-cf0e-c72e-7acc-518b736e715e@colorfullife.com>
On Mon, Sep 05, 2016 at 08:57:19PM +0200, Manfred Spraul wrote:
> On 09/02/2016 09:22 PM, Peter Zijlstra wrote:
> Anyone around with a ppc or arm? How slow is the loop of the
> spin_unlock_wait() calls?
> Single CPU is sufficient.
>
> Question 1: How large is the difference between:
> #./sem-scalebench -t 10 -c 1 -p 1 -o 4 -f -d 1
> #./sem-scalebench -t 10 -c 1 -p 1 -o 4 -f -d 256
> https://github.com/manfred-colorfu/ipcscale
Not sure exactly what you want me to run here, but with an arm64
defconfig -rc3 kernel, those two invocations give me "Max total" values
where the first is 20x bigger than the second.
Will
prev parent reply other threads:[~2016-09-06 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 15:27 [PATCH 8/7] net/netfilter/nf_conntrack_core: Remove another memory barrier Manfred Spraul
2016-09-01 15:27 ` [PATCH 9/7] ipc/sem.c: " Manfred Spraul
2016-09-01 15:30 ` [PATCH 8/7] net/netfilter/nf_conntrack_core: " Will Deacon
2016-09-01 16:41 ` Peter Zijlstra
2016-09-02 6:17 ` Boqun Feng
2016-09-02 6:35 ` Manfred Spraul
2016-09-02 19:22 ` Peter Zijlstra
2016-09-03 5:33 ` Manfred Spraul
2016-09-05 18:57 ` Manfred Spraul
2016-09-06 17:56 ` Will Deacon [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=20160906175648.GC29382@arm.com \
--to=will.deacon@arm.com \
--cc=1vier1@web.de \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mingo@elte.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.