DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=KUjFUddyHPdww8IPA530th3sLsUBPxOSC03FTCtOJkXohxTl7G6/qbG0fygqEBFmK9
         i+ObwJXsHKGtxu7vetDSuKnpSxAOrE2j5aWiDjSb+zkC+2W0lpXGZKE6E087PvmZlBQa
         eLPl0JBS8yXfDPJcKNC/miqrf8aQUDRMXOdxc=
MIME-Version: 1.0
Date: Mon, 26 Oct 2009 22:49:30 +0530
Message-ID: <f22d86810910261019yc77dbf0sa7688a98e7b98267@mail.gmail.com>
Subject: Difference between atomic operations and memory barriers
From: "Leonidas ." <leonidas137@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 775
Lines: 23

Trying to understand difference between atomic ops and memory barriers.

I was thinking all atomic operations must be using barrier internally,
but I read
somewhere that only some of them use barriers. Sorry for being vague here.

Operations before call to smp_mb() will not be re-ordered and all cpus will see
consistent value after the variable is updated.

E.g.
void * ptr = (void *) str;
smb_mb();

Will this not atomically update ptr? Ptr will be seen by all cpu's in
same state
after it has been assigned str, right?

-Leo.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/