site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com User-agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) Dear Friends, Thank you, Alejandro -- Alejandro Palencia Open Studio Networks +34 667 440 770 _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... I am running very low latency real-time threads (for audio purposes) on 6 cpus and other admin threads on the other 2 cpus, including disk I/O threads. When reading audio from disk, the real-time threads get stucked at random times. I believe that this interaction is because the disk read command launches a lower-half kernel thread that can run any of the 8 cpus, and the memory movement from disk to RAM invalidates their caches and breaks their real-time behavior. Is there any solution? For example, prohibiting the kernel threads to run on particular cpus or bound them to a cpu? This email sent to site_archiver@lists.apple.com