On Thu, Mar 8, 2012 at 10:46 AM, Per Bull Holmen <pbhol...@gmail.com> wrote: > Den 23:55 7. mars 2012 skrev Don Quixote de la Mancha > <quix...@dulcineatech.com> følgende: > >> If you possibly can replace locking algorithms with what are commonly but >> incorrectly called lock free algorithms. They use Atomic Arithmetic >> Primitives provided by the CPU Instruction Set Archetector to manage very >> short term locks on single words of memory. > > Lock-free algorithms are cool, but keep in mind that they can be hard > to implement, so you have to know what you're doing. Once you have > forgotten to think of a possible scheduling sequence that might > corrupt your data, you have introduced very subtle bugs that can be > very hard to track down. And it may not scale... What if the program runs virtualized? Memory locks on one machine are not honored on a separate, virtualized server.
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
