From: Elias Oltmanns <eo@nebensachen.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] SCSI: Fix some locking issues
Date: Thu, 03 Jul 2008 09:12:26 +0200 [thread overview]
Message-ID: <87abgz30h1.fsf@denkblock.local> (raw)
In-Reply-To: <20080702162306.GV14894@parisc-linux.org> (Matthew Wilcox's message of "Wed, 2 Jul 2008 10:23:06 -0600")
Matthew Wilcox <matthew@wil.cx> wrote:
> On Wed, Jul 02, 2008 at 05:59:31PM +0200, Elias Oltmanns wrote:
>> > The reason no locks are necessary is that there's no race to mediate.
>
>> > The checks are only is it set or not ...
>>
>> I'm not sure whether that is of any consequence. Don't get me wrong, I
>> really don't know and you may well be right. But how exactly does
>> decrementing from 2 to 1 work? Do we know for sure that there will
>> always be at least one bit set so reading that address will reliably
>> return a non zero value?
>
> The assumption we make (and it is believed to be true on all SMP systems)
> is that a write to a naturally aligned memory location that is sized <=
> sizeof(long) is atomic. That is, a reader will get either the previous
> value or the subsequent value, not a mixture. The RCU code relies
> heavily on this assumption.
Does that mean that where ever I have
spin_lock_irqsave(some_lock, flags);
var = some_val;
spin_unlock_irqrestore(some_lock, flags);
I could just as well discard the locking provided that
sizeof(var) <= sizeof(long)
because the assignment of some_val to var will be atomic anyway?
Regards,
Elias
next prev parent reply other threads:[~2008-07-03 7:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 11:38 [PATCH] SCSI: Fix some locking issues Elias Oltmanns
2008-07-01 21:37 ` Elias Oltmanns
2008-07-02 1:55 ` James Bottomley
2008-07-02 7:08 ` Elias Oltmanns
2008-07-02 11:50 ` Jens Axboe
2008-07-02 14:49 ` James Bottomley
2008-07-02 18:45 ` Jens Axboe
2008-07-02 20:18 ` James Bottomley
2008-07-03 7:53 ` Elias Oltmanns
2008-07-03 10:38 ` Elias Oltmanns
2008-07-03 11:24 ` Jens Axboe
2008-07-03 16:31 ` James Bottomley
2008-07-03 17:54 ` Jens Axboe
2008-07-03 19:47 ` Elias Oltmanns
2008-07-03 21:33 ` James Bottomley
2008-07-02 14:46 ` James Bottomley
2008-07-02 15:59 ` Elias Oltmanns
2008-07-02 16:23 ` Matthew Wilcox
2008-07-03 7:12 ` Elias Oltmanns [this message]
2008-07-03 15:22 ` James Bottomley
2008-07-03 19:39 ` Elias Oltmanns
2008-07-03 15:47 ` Matthew Wilcox
2008-07-02 16:32 ` James Bottomley
2008-07-03 7:25 ` Elias Oltmanns
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=87abgz30h1.fsf@denkblock.local \
--to=eo@nebensachen.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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).