From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Add SWP/SWPB emulation for ARMv7 processors
Date: Thu, 17 Dec 2009 19:16:02 +0000 [thread overview]
Message-ID: <20091217191602.GC362@shareable.org> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE896716203A7FA69CC@dlee02.ent.ti.com>
Woodruff, Richard wrote:
> Exclusive operations are more certainly more efficient than the full
> bus lock behavior of SWP. Finding and killing SWP where possible
> seems positive.
Are they really more efficient for cached accesses in L1? In
principle, external bus lock is not needed when doing an
read-modify-write on words in MESI cache, just the ability to
internally block it's eviction during the sequence.
-- Jamie
next prev parent reply other threads:[~2009-12-17 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 17:54 [PATCH] ARM: Add SWP/SWPB emulation for ARMv7 processors Leif Lindholm
2009-12-17 18:19 ` Woodruff, Richard
2009-12-17 19:16 ` Jamie Lokier [this message]
2009-12-17 20:43 ` Woodruff, Richard
2009-12-18 20:31 ` Jamie Lokier
2010-01-08 23:20 ` Woodruff, Richard
2009-12-18 14:15 ` Leif Lindholm
2009-12-17 19:32 ` Jamie Lokier
2009-12-18 10:00 ` Catalin Marinas
2009-12-18 10:06 ` Catalin Marinas
2009-12-18 17:01 ` Leif Lindholm
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=20091217191602.GC362@shareable.org \
--to=jamie@shareable.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 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.