{"id":32738,"date":"2021-06-07T11:17:54","date_gmt":"2021-06-07T15:17:54","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=32738"},"modified":"2021-06-07T11:17:54","modified_gmt":"2021-06-07T15:17:54","slug":"kernel-assisting-the-objective-c-runtime","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2021\/06\/07\/kernel-assisting-the-objective-c-runtime\/","title":{"rendered":"Kernel Assisting the Objective-C Runtime"},"content":{"rendered":"

This is really cool, and I just realized that I forgot to link to it after last year’s WWDC.<\/p>\n\n

Pierre Habouzit<\/a>:<\/p>\n

Faster, priority-inversion-less GC (speed)<\/p>

@mikeash wrote about it a long time ago<\/a>, however it turns out this was relatively slow and could also fail (if a thread was observed in the critical section).<\/p>

The general idea is still the same, but instead of observing the other threads PC, we use a scheme where at startup the runtime tells the kernel where the code reading the IMP caches “unsafely” is, and gives a “recovery PC”.<\/p>

Now when a GC is triggered, instead of asking for all the other threads PCs, the kernel is told to “force” the PC of threads in the critical section to the recovery path, there’s no waiting, and it can’t fail.<\/p>

it’s also 10-100x as fast as before.<\/p><\/blockquote>\n\n

David Smith<\/a>:<\/p>\n

This is one of the wildest optimizations I’ve seen. How do you make a reader-writer lock with zero instructions? You uh… ask the kernel to move all the reader threads out of the critical section 😱😱😱<\/p>

Just like… longjmp someone else from outside 🤯<\/p><\/blockquote>\n\n

Pierre Habouzit<\/a>:<\/p>\n

I really feel that working at \n@Apple\n gives one a unique convergence of “all the things” that is mostly unmatched in the rest of the industry and some of us are lucky enough to have the opportunity to take advantage of it ;)<\/p><\/blockquote>\n\n

Previously:<\/p>\n