[Vm-dev] linux thread priorities
John M McIntosh
johnmci at smalltalkconsulting.com
Thu Feb 4 05:44:19 UTC 2010
Well mmm doesn't the checkForInterrupts code get called every 1 millisecond (or there about?)
Can't you add something there to ensure your sound logic doesn't starve.
Hint if checkForInterrupts is not being called every ms or so how do you ensure delay accuracy is to a ms boundary?
next hint if checkForInterrupts is being called 10 times a millisecond then isn't that wasteful, should you be grinding smalltalk bytecodes or assembler instructions there of?
On 2010-02-03, at 6:01 PM, Eliot Miranda wrote:
> I've been trying to get our sound framework going on linux and have got stuck. I wondered whether anyone has any experience getting round this problem on linux. It is complicated so excuse the lengthy explanation.
> Our sound processing depends on a high-prirority thread running for a short time every 20 milliseconds to push data through the sound processing paths (microphone recording, OpenAL for spatialization, and so on). On linux this approach is not immediately applicable because (*)
John M. McIntosh <johnmci at smalltalkconsulting.com> Twitter: squeaker68882
Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev