Re: kStreamIoctlEvent and T_MEMORYRELEASED question
Re: kStreamIoctlEvent and T_MEMORYRELEASED question
- Subject: Re: kStreamIoctlEvent and T_MEMORYRELEASED question
- From: Quinn <email@hidden>
- Date: Thu, 11 Mar 2004 11:07:02 +0000
At 13:17 -0700 10/3/04, Thomas E. Knowlton, Jr. wrote:
Is there any kind of guaranty as to when kStreamIoctlEvent arrives
relative to the T_MEMORYRELEASED events, after calling
TEndpoint::Ioctl(I_FLUSH, FLUSHRW)?
No. There are no guarantees at all abou the ordering of
T_MEMORYRELEASED events.
In other words, can I rely on having received all T_MEMORYRELEASED
events before I get notified of kStreamIoctlEvent?
No.
Alternatively, since T_MEMORYRELEASED is allowed to reenter the
notifier, is it allowable to spin in a loop to handle
kStreamIoctlEvent, breaking out when the T_MEMORYRELEASED handler
sets the appropriate state indicating "the last one"?
No! Under no circumstances should you spin in a notifier.
What's the actual problem you're trying to solve?
S+E
--
Quinn "The Eskimo!" <
http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.