public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Leonidas ." <leonidas137@gmail.com>,
	Chris Friesen <cfriesen@nortel.com>,
	Noah Watkins <noah@noahdesu.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Difference between atomic operations and memory barriers
Date: Wed, 28 Oct 2009 12:00:05 +0200	[thread overview]
Message-ID: <4AE81625.5000500@panasas.com> (raw)
In-Reply-To: <45208.1256644303@turing-police.cc.vt.edu>

On 10/27/2009 01:51 PM, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 27 Oct 2009 00:30:45 +0530, "Leonidas ." said:
> 
>> So we can safely assume that pointer assignment will be done in an
>> atomic manner?
> 
> Has anybody ever actually made a *production* CPU that had non-atomic
> pointer assignments?  And how long before the crazed programmers lynched
> and burned the offending CPU designer at the stake? ;)
> 
> Non-atomic pointer assignments are the CPU design equivalent of Vogon poetry.
> Just Say No. With a shotgun if needed.

What don't you know? the CPU that started it all was like that, the x86 16-bit
"large" and "huge" model had a double register seg:offset set, also in-memory
was double-ints(2*16) even the i386 was running 16 bit modes for a long time.

Kernel still have 16-bit dosemu mode supported until today, no?

About the shotguns lynching and burning I'm not sure, but Intel survived
just fine.

Boaz

  reply	other threads:[~2009-10-28 10:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 17:19 Difference between atomic operations and memory barriers Leonidas .
     [not found] ` <7ADB5FD7-9C97-4987-BC20-997258B25FD2@noahdesu.com>
2009-10-26 18:22   ` Leonidas .
2009-10-26 18:54     ` Chris Friesen
2009-10-26 19:00       ` Leonidas .
2009-10-26 19:07         ` Noah Watkins
2009-10-26 19:34           ` Stefan Richter
2009-10-26 19:42             ` Noah Watkins
2009-10-27 11:51         ` Valdis.Kletnieks
2009-10-28 10:00           ` Boaz Harrosh [this message]
2009-10-28 13:26             ` Valdis.Kletnieks
2009-10-26 19:00     ` Stefan Richter
2009-10-26 19:05       ` Leonidas .
2009-10-27 10:21         ` Michael Schnell
2009-10-27 10:23           ` Leonidas .
2009-10-27 11:01             ` Michael Schnell
2009-10-27 14:57             ` Stefan Richter

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=4AE81625.5000500@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=cfriesen@nortel.com \
    --cc=leonidas137@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noah@noahdesu.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