[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0709080429420.27088@twinlark.arctic.org>
Date: Sat, 8 Sep 2007 04:34:03 -0700 (PDT)
From: dean gaudet <dean@...tic.org>
To: Nick Piggin <nickpiggin@...oo.com.au>
cc: Linus Torvalds <torvalds@...ux-foundation.org>, ak@...e.de,
Jesse Barnes <jesse.barnes@...el.com>,
linux-kernel@...r.kernel.org
Subject: Re: Intel Memory Ordering White Paper
On Sun, 9 Sep 2007, Nick Piggin wrote:
> I've also heard that string operations do not follow the normal ordering, but
> that's just with respect to individual loads/stores in the one operation, I
> hope? And they will still follow ordering rules WRT surrounding loads and
> stores?
see section 7.2.3 of intel volume 3A...
"Code dependent upon sequential store ordering should not use the string
operations for the entire data structure to be stored. Data and semaphores
should be separated. Order dependent code should use a discrete semaphore
uniquely stored to after any string operations to allow correctly ordered
data to be seen by all processors."
i think we need sfence after things like copy_page, clear_page, and
possibly copy_user... at least on intel processors with fast strings
option enabled.
-dean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists