Re: Socket recv behaviour in real-time context
Re: Socket recv behaviour in real-time context
- Subject: Re: Socket recv behaviour in real-time context
- From: Stéphane Letz <email@hidden>
- Date: Sun, 15 Mar 2009 20:16:09 +0100
Message: 1
Date: Sat, 14 Mar 2009 17:45:46 -0700
From: Jeff Moore <email@hidden>
Subject: Re: Socket recv behaviour in real-time context
To: CoreAudio API <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes
I don't really know a whole lot about sockets or our network stack.
But, your description of the problem sounds like there could be a
priority inversion problem on your slave machine. Even though the
thread you have servicing the socket is a real time thread, I'd bet
good money that the thread in the kernel that feeds the socket is not.
This means that the more activity you have in your real time threads
(including the HAL's IO thread or any MIDI threads) will cause
scheduling latency for lower priority threads.
That said, 50 milliseconds seems completely crazy. You'd have to have
an awful lot of real time threads doing work to get that kind of
scheduling latency. Have you gotten any kernel traces?
On Mar 13, 2009, at 10:30 AM, Stéphane Letz wrote:
What kind of tools can be used in this case?
Thanks
Stéphane Letz _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden