Locking pages in physical memory for real-time processes
Locking pages in physical memory for real-time processes
- Subject: Locking pages in physical memory for real-time processes
- From: Stéphane Letz <email@hidden>
- Date: Thu, 6 May 2004 13:03:17 +0200
Hi,
After discussion with Linux guys about memory issues for real-time
processes, I was wondering what is the corrrect solution on MacOSX.
Linux developers usually use mlockall kind of call to lock pages in
physical memory for data (audio buffers) and some of them were even
thinking in locking page for the code.
I read some older mails about the subject without clear view of what
has to be done.
Is mlockall kind of call usable on MacOSX, is is really necessary, or
can we trust the memory manager to handle that correctly? Are they any
other standard techniques ; preloding data... but maybe other ideas?
Thanks in advance
Stephane Letz
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.