That it actually quite simple and nifty. It reminds me of the 4 priorities RPC requests can have within the Google stack. 0 being if this fails it will result in a big fat error for the user to 3, we don’t care if this fails because we will run the analysis job again in a month or so.
IIRC in macOS you do need to pass the voucher, it isn’t inherited automatically. Linux has no knowledge of it, so first it has to be introduced as a concept and then apps have to start using it.
Re:Why E cores make Apple silicon fast
by saagarjha on Monday February 09, 2026 @05:43AM
(#46943790)
There is automatic priority donation across a handful of APIs
Re:Why E cores make Apple silicon fast
by surajrmal on Monday February 09, 2026 @07:18AM
(#46944437)
Being explicit is a good thing. Especially for async threads they may handle work for many different clients with different priorities and may delegate work to other processes.
This sounds like Solaris doors. The remainder of the time slice of the door client is given to the door server.
This lets Apple architect things as small, single-responsibility processes, but make their priority dynamic, such that they’re usually low-priority unless a foreground user process is blocked on their work. I’m not sure the Linux kernel has this.