[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Spinlocks and volatile

To: Thanos Makatos <mcatos@xxxxxxxxxxxx>
Subject: Re: Spinlocks and volatile
From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 10 Dec 2008 18:40:13 +0100
Cc: kernelnewbies@xxxxxxxxxxxx
In-reply-to: <493FD31D.4090607@ics.forth.gr>
List-archive: <http://mail.nl.linux.org/kernelnewbies/>
List-help: <mailto:ecartis@nl.linux.org?Subject=help>
List-id: <kernelnewbies.nl.linux.org>
List-owner: <mailto:ecartis-owner@nl.linux.org>
List-post: <mailto:kernelnewbies@nl.linux.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=subscribe>
List-unsubscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=unsubscribe>
References: <493FD31D.4090607@ics.forth.gr>
Sender: kernelnewbies-bounce@xxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)

Hi!

On 16:33 Wed 10 Dec     , Thanos Makatos wrote:
> Do shared variables only accessed inside spinlocks have to be declared as volatile?

No, see Documentation/volatile-considered-harmful.txt
	-Michi
-- 
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com


--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ

References:
- Spinlocks and volatile
  - From: Thanos Makatos

Prev by Date: Spinlocks and volatile
Next by Date: Interrupts only on one core on a dual core machines.
Previous by thread: Spinlocks and volatile
Next by thread: Interrupts only on one core on a dual core machines.
Index(es):
- Date
- Thread