From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: crazy spinlock speed test.
Date: Wed, 24 Feb 2010 16:55:38 +0100 [thread overview]
Message-ID: <20100224155538.GB5130@linux-mips.org> (raw)
In-Reply-To: <1266362795-20199-1-git-send-email-ddaney@caviumnetworks.com>
On Tue, Feb 16, 2010 at 03:26:35PM -0800, David Daney wrote:
> This is just a test program for raw_spinlocks. The main reason I
> wrote it is to validate my spinlock changes that I sent in a previous
> patch.
>
> To use it enable CONFIG_DEBUG_FS and CONFIG_SPINLOCK_TEST then at run
> time do:
>
> # mount -t debugfs none /sys/kernel/debug/
> # cat /sys/kernel/debug/mips/spin_single
> # cat /sys/kernel/debug/mips/spin_multi
>
> On my 600MHz octeon cn5860 (16 CPUs) I get
>
> spin_single spin_multi
> base 106885 247941
> spinlock_patch 75194 219465
>
> This shows that for uncontended locks the spinlock patch gives 41%
> improvement and for contended locks 12% improvement (1/time).
>
> Signed-off-by: David Daney <ddaney@caviumnetworks.com>
Also queued for 2.6.34.
Thanks!
Ralf
prev parent reply other threads:[~2010-02-24 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 23:26 [PATCH] MIPS: crazy spinlock speed test David Daney
2010-02-24 15:55 ` Ralf Baechle [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=20100224155538.GB5130@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox