Joe Seigh wrote:
For synchronization you need memory barriers in most cases and the only
way to get these is using assembler since there are no C or gcc intrinsics
for these yet. For inline assembler, the convention seems to be to use
the volatile attribute, which I take as meaning no code
ve no effect on performance in this case. You're seeing the most
"recent" value due to the cache implementation.
--
Joe Seigh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at htt
Joe Seigh wrote:
A bit sketchy. You can see a working example of this using
C++ refcounted pointers (which can't be used in the kernel
naturally, you'll have to implement your own) at
http://atomic-ptr-plus.sourceforge.net/
The APPC stuff is in the atomic-ptr-plus package if
ollector objects have
deallocation performed on them and attached nodes.
A bit sketchy. You can see a working example of this using
C++ refcounted pointers (which can't be used in the kernel
naturally, you'll have to implement your own) at
http://atomic-ptr-plus.sourceforge.net/
--
Joe
4 matches
Mail list logo
