Assume it’s multiprocessor-safe


As Matthew Dillon notes in a recent post, procedures are now assumed to be MPSAFE (i.e. without the Giant Lock) by default.  Any new work should follow this idea, and it doesn’t have to be documented specially.  The inverse used to be true, where the code that happened to work without the Lock was rare, and therefore needed to be pointed out.   Now, the good result is the norm.

Posted by     Categories: Committed Code, DragonFly, Goings-on     0 Comments
0 Comments on Assume it’s multiprocessor-safe

Respond | Trackback

Respond

Comments

Comments