• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Locking pages in physical memory for real-time processes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Locking pages in physical memory for real-time processes


  • Subject: Re: Locking pages in physical memory for real-time processes
  • From: John Stiles <email@hidden>
  • Date: Thu, 6 May 2004 14:05:50 -0700

On May 6, 2004, at 12:42 PM, Doug Wyatt wrote:

- explicitly zero newly allocated buffers that will be accessed at audio render time. Replacing malloc() with calloc() is one way.

My understanding of calloc was that it used a trick of the MMU (mapping each block in the allocation to one copy-on-write page full of zeros) and did not actually touch physical memory.
_______________________________________________
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.


References: 
 >Locking pages in physical memory for real-time processes (From: Stéphane Letz <email@hidden>)
 >Re: Locking pages in physical memory for real-time processes (From: David Duncan <email@hidden>)
 >Re: Locking pages in physical memory for real-time processes (From: Doug Wyatt <email@hidden>)

  • Prev by Date: Re: The new AU SDK / AudioStreamBasicDescription
  • Next by Date: Re: Locking pages in physical memory for real-time processes
  • Previous by thread: Re: Locking pages in physical memory for real-time processes
  • Next by thread: Re: Locking pages in physical memory for real-time processes
  • Index(es):
    • Date
    • Thread