Understanding OS X Kernel Internals

jglidell writes "The OS X kernel has been in the news alot this past year, whether it's why its slow, Mach/micro-kernel makes it bad, it's going closed source and what not. Amit Singh has put up a new presentation on the innards of OS X. It does a pretty good job of summing up the OS X kernel architecture, and has some pretty detailed diagrams... for instance they show that there are so many process/threads layers in OS X. So if you are in the mood for doing some OS studying then head over."

Comments

Re:Spelling

[mangu]

"alot" isn't a word! It's "a lot."

I also get kinda pissed off because lotsa people write it that way.

Re:Needs more editor.

[gowen]

I think the problem is that they're not as skilled in writing english as they are in writing PERL.

I've seen slashcode.

I think the problem is that they're exactly as skilled in writing english as they are in writing PERL.

Re:huh?

[M. Baranczak]

Nope, it's still gibberish.

whether it's why it's slow

Well... why is it slow?

Mach/micro-kernel makes it bad

Debating the pros and cons of Mach is a valid topic, but a phrase like this is so vague that it's meaningless.

it's going closed source

OK, that one's intelligible. But then we come across gems like this:

for instance they show that there are so many process/threads layers in OS X.

A small request for submitters: Take a minute to actually proof-read your summary. I'm not even talking about simple typos, or the correct use of "you're/your" - those look ugly, but most of the time people can still figure out what you meant. Just ask yourself: will these words make sense to a moderately intelligent English speaker who's not on a meth bender?