public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
	Kernel@smtp1.linux-foundation.org,
	Zdenek@smtp1.linux-foundation.org,
	development list <linux-kernel@vger.kernel.org>,
	Kabelac <zdenek.kabelac@gmail.com>,
	pm list <linux-pm@lists.linux-foundation.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	davem@davemloft.net, Pierre Ossman <drzeus-mmc@drzeus.cx>
Subject: Re: [patch] Re: using long instead of atomic_t when only set/read is required
Date: Mon, 3 Mar 2008 17:33:40 +0000	[thread overview]
Message-ID: <20080303173340.55a38c6b@core> (raw)
In-Reply-To: <200803040416.33937.nickpiggin@yahoo.com.au>

> Are you sure gcc doesn't? Or is it just "C"?

gcc doesn't

> Linux wouldn't work today if gcc did something non-atomic there
> (presuming you're talking about naturally aligned pointers/ints).
> It is widely used and accepted.

Yes and we've had tty layer traces in the past clearly showing it isn't
always safe, especially if any math is involved anywhere near the
assignment. That may be why pointer flipping happens to work.

Alan

  parent reply	other threads:[~2008-03-03 17:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080225090316.GA420@elf.ucw.cz>
2008-02-25 14:46 ` using long instead of atomic_t when only set/read is required (was Re: [Bug 10030] Suspend doesn't work when SD card is inserted) Alan Stern
     [not found] ` <Pine.LNX.4.44L0.0802250943410.3549-100000@iolanthe.rowland.org>
2008-03-03 12:08   ` [patch] Re: using long instead of atomic_t when only set/read is required Pavel Machek
     [not found]   ` <20080303120842.GA28369@elf.ucw.cz>
2008-03-03 15:42     ` Alan Stern
2008-03-03 15:48     ` Alan Cox
     [not found]     ` <Pine.LNX.4.44L0.0803031023550.3611-100000@iolanthe.rowland.org>
2008-03-03 15:53       ` Alan Cox
     [not found]       ` <20080303155330.39e45ad4@core>
2008-03-03 17:11         ` Alan Stern
2008-03-03 17:16         ` Nick Piggin
2008-03-03 17:31           ` Paul E. McKenney
2008-03-03 17:33           ` Alan Cox [this message]
2008-03-03 17:22       ` Paul E. McKenney
     [not found]     ` <20080303154831.22a4eb14@core>
2008-03-03 17:24       ` Pavel Machek
2008-03-03 20:27         ` Rafael J. Wysocki
     [not found]         ` <200803032127.30761.rjw@sisk.pl>
2008-03-03 21:12           ` Paul E. McKenney
2008-03-03 22:23           ` Linus Torvalds
     [not found] <Pine.LNX.4.44L0.0803031207120.3611-100000@iolanthe.rowland.org>
2008-03-03 17:26 ` Linus Torvalds
2008-03-03 17:44   ` Pavel Machek
2008-03-06 15:58   ` Mark Lord
     [not found]   ` <47D014A6.9090300@rtr.ca>
2008-03-06 16:11     ` Linus Torvalds
     [not found]     ` <alpine.LFD.1.00.0803060807120.12253@woody.linux-foundation.org>
2008-03-06 16:27       ` Mark Lord
     [not found] <20080303174422.GB13869@elf.ucw.cz>
2008-03-03 19:27 ` Alan Stern

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=20080303173340.55a38c6b@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Kernel@smtp1.linux-foundation.org \
    --cc=Zdenek@smtp1.linux-foundation.org \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=zdenek.kabelac@gmail.com \
    /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