site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Yeah, but... 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: Bad advice. For exact this reason. Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/francini%40mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... 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. Allocate it not with malloc, but with vm_allocate, then vm_wire it. This avoids paging [...] If more developers develop such habits, we're back in the Mac OS 9 days quickly. This email sent to francini@mac.com This email sent to site_archiver@lists.apple.com