Subject: SCE-MI Service Loop: Some Questions
From: Bojsen, Per (bojsen@zaiqtech.com)
Date: Fri Dec 12 2003 - 18:06:43 PST
Hi,
this was originally sent to Brian and Duaine and Brian asked me to
forward it to the mailing list. Hopefully the list is up now.
I have some questions regarding the SCE-MI service loop:
1) It is not clear to me whether the g() callback must be called
for each message transferred or whether the SCE-MI service
loop can transfer everything it knows about first, and then
call g()? Actually, I am reading example 5.3.3.6.1 again
and in that example it states that g() is called for each
message processed. Does this refer to only input messages,
or both input and output messages?
2) The pending argument of g() is supposed to indicate whether
there is at least one message pending. It is not clear whether
this refers to input messages, output messages, or both. Input
messages makes sense to me, but it may not be possible for the
service loop to know whether output messages are pending on the
hardware side. In the fourth paragraph from the bottom of
p. 43, there is a distinction between messages `pending to be
sent' and 'arriving messages'. This would seem to support the
interpretation that only input messages figure in the pending
argument.
Thanks,
Per
-- Per Bojsen Email: <bojsen@zaiqtech.com> Zaiq Technologies, Inc. WWW: http://www.zaiqtech.com 78 Dragon Ct. Tel: 781 721 8229 Woburn, MA 01801 Fax: 781 932 7488
This archive was generated by hypermail 2b28 : Mon Jan 05 2004 - 07:32:37 PST