does anyone know of a fairly comprehensive rules to follow for Linux kernel code (or any other kernel)? not talking about coding style but rather stuff like "keep interrupt handlers below 5 microseconds" or "don't touch user-mode memory directly"
-
-
I remember that many years ago (pre-win2k) at Microsoft there was supposed to be this one guy who fully understood NTFS locking
-
Does that means that there exists someone that fully understand locking ? Is it a human ?
End of conversation
New conversation -
-
-
It's no accident that musl mostly avoids having internal interfaces at all; not having them means not having to document/specify them.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.