On Tue, Feb 27, 2018 at 5:10 PM, Brian Armstrong < [email protected]> wrote:
> Also, in the context of things that could block, it's certainly possible > that reading/writing to a large array will hit an unmapped page, which I > believe will context switch your thread out. I don't know that any OS makes > guarantees for how long a page fault could take. I think it's not generally > possible to make such guarantees with virtual memory. > that's why you use memlock(2) or equivalent on code and data that will run in realtime context.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
