The earlier lines of discussion made it obvious that this application
needs to have near-real-time levels of predictable response. Having the
OS decide to page on you when you really don't want it to do so doesn't
help, and makes the platform look like it's inhospitable to real-time
use. Most ordinary applications don't need that sort of predictable
response pattern, but this one does.
Sounds like a potentially workable solution to me...
John Francini
On Jul 27, 2005, at 9:54, Markus Hitter wrote:
Am 27.07.2005 um 10:41 schrieb Jan Brittenson:
Allocate it not with malloc, but with vm_allocate, then vm_wire it.
Bad advice.
This avoids paging [...]
For exact this reason.
If more developers develop such habits, we're back in the Mac OS 9
days quickly.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
