From: ashwinc@codeaurora.org (Ashwin Chaugule)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] [PATCH] XCHGADD ARM implementation
Date: Tue, 05 Oct 2010 17:05:55 -0400 [thread overview]
Message-ID: <4CAB9333.50400@codeaurora.org> (raw)
The following patch is the ARM implementation for RWSEM_XCHGADD_ALGORITHM.
Based on David's rwsem benchmark from http://lwn.net/Articles/89191/ ,
I see a consistent 5-6% increase in the number of reads and writes taken as
compared to RWSEM_GENERIC_SPINLOCK on a dual core ARMv7. So far I have tested
numrd=1 numwr=1 numdg=1 do_sched=1
numrd=10 numwr=10 numdg=1 do_sched=1
numrd=20 numwr=20 numdg=1 do_sched=1
Can anyone else help to test this patch on other ARM systems ?
Cheers,
Ashwin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Optimzed-ARM-RWSEM-algorithm.patch
Type: text/x-patch
Size: 5928 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20101005/12e3b202/attachment.bin>
reply other threads:[~2010-10-05 21:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CAB9333.50400@codeaurora.org \
--to=ashwinc@codeaurora.org \
--cc=linux-arm-kernel@lists.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 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).