From: dhylands@gmail.com (Dave Hylands)
To: linux-arm-kernel@lists.infradead.org
Subject: your mail
Date: Mon, 7 Jun 2010 15:44:16 -0700 [thread overview]
Message-ID: <AANLkTikA_eXw1fMwOtuPxLqlDdzz4IYJfsXkpuCSkOUw@mail.gmail.com> (raw)
In-Reply-To: <20100607221047.GA27304@shareable.org>
HI Jamie,
On Mon, Jun 7, 2010 at 3:10 PM, Jamie Lokier wrote:
> Dave Hylands wrote:
[...]
>> Another way of asking this: If both cores are writing to the same
>> 32-bit word (but different bytes) do the writes collide?
>
> I'm pretty sure any system compatible with pthreads has to be fine
> with the variables being independent, because the bytes could be
> variables protected by separate mutexes.
>
> However, other questions for your lockless structures are whether
> writes by one processor are seen in a reasonable or even bounded time
> by reads on another processor (write buffering), and which barrier
> instructions to use between the index accesses and accessing some
> array they might indexing (only a problem for userspace, because the
> kernel already provides barriers).
After lots of reading - I think that the Snoop Control Unit takes care
of moving the cache lines from one core to the other when both cores
are trying to access data from the same cache line.
So it's not very efficient to have both cores accessing data from the
same cache line - but it seems that the integrity of the data should
be maintained (or at least this is my current understanding).
--
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/
next prev parent reply other threads:[~2010-06-07 22:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 17:58 No subject Dave Hylands
2010-06-07 22:10 ` your mail Jamie Lokier
2010-06-07 22:44 ` Dave Hylands [this message]
[not found] <20191026192359.27687-1-frank-w@public-files.de>
2019-10-26 19:30 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2017-06-04 11:59 No subject Yury Norov
2017-06-14 20:16 ` your mail Yury Norov
2015-04-21 10:18 No subject Ard Biesheuvel
2015-04-21 10:46 ` your mail Dave P Martin
2015-04-21 10:50 ` Ard Biesheuvel
2015-04-21 11:10 ` Dave P Martin
2015-04-21 11:15 ` Ard Biesheuvel
2015-04-21 11:24 ` Russell King - ARM Linux
2015-04-21 12:50 ` Russell King - ARM Linux
2015-04-21 13:10 ` Ard Biesheuvel
2015-04-21 13:21 ` Dave P Martin
2015-04-21 13:28 ` Ard Biesheuvel
2015-04-21 15:51 ` Dave Martin
2015-04-21 14:05 ` Russell King - ARM Linux
2015-04-21 13:18 ` Dave P Martin
2015-04-21 13:55 ` Russell King - ARM Linux
2015-04-21 14:06 ` Ard Biesheuvel
2015-04-21 17:03 ` Dave Martin
2014-10-28 14:13 No subject Mark Rutland
2014-10-28 14:19 ` your mail Mark Rutland
2012-06-21 18:26 No subject Paul Walmsley
2012-06-22 8:56 ` your mail Tony Lindgren
2011-12-02 16:01 No subject Will Deacon
2011-12-02 16:11 ` your mail Will Deacon
2011-05-13 19:35 No subject Vadim Bendebury
2011-05-14 3:32 ` your mail Jean-Christophe PLAGNIOL-VILLARD
2010-05-18 10:38 No subject Marek Szyprowski
2010-05-19 2:24 ` your mail Ben Dooks
[not found] <1250258343-14203-1-git-send-email-thierry.reding@avionic-design.de>
2009-10-02 14:53 ` Thierry Reding
2010-01-02 12:06 ` Russell King - ARM Linux
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=AANLkTikA_eXw1fMwOtuPxLqlDdzz4IYJfsXkpuCSkOUw@mail.gmail.com \
--to=dhylands@gmail.com \
--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).