SCTP Discussions

Text archives Help


[SCTP-Discussion] OS-support for Timer service


Chronological Thread 
  • From: Schruefer Wolfgang <Wolfgang.Schruefer AT icn.siemens.de>
  • To: discussion AT sctp.de
  • Subject: [SCTP-Discussion] OS-support for Timer service
  • Date: Thu Mar 1 17:18:02 2001
  • List-id: SCTP Discussions <discussion.sctp.de>

Dear all,

I just forward a hint of Joel Wagner (developer at SOLARIS-kernel) and
Juergen Luckas (diveloper at NUCLEUS), which I will post here:

(Both want to replace the sctp-internal timer-service from adaptation.c by
OS-supported timerservice.)

a)[Joel] The Solaris kernel timer primitives only support 1 user defined
pointer, not the 2 that you request. Is it possible that the generic SCTP
could be modified to get by with just 1 pointer? It would be good to check
what VxWorks, MBDE's operating environment, and maybe Linux provide. If
other environments only provide 1 user defined pointer then it might be
best to change the generic to be less demanding of the operating
environment.

>[Juergen] hi guys,
the operating system nucleus supports one user defined
parameter.
This timer ID is a parameter unsigned int (4 bytes). I think it can be used
as one pointer, too.
Gruesse
Juergen


b)[Joel]Can the requirement for the adaptation layer to support a "restart
timer" be removed? The generic SCTP can achieve a restart by issuing a
"stop timer" followed by a "start timer".



Viele Gruesse
Wolfgang

**************************************
Wolfgang Schrüfer SIEMENS AG
ICN WN CC EKJ 14 TEL: 722-61646
mailto:Wolfgang.Schruefer AT icn.siemens.de
**************************************




  • [SCTP-Discussion] OS-support for Timer service, Schruefer Wolfgang, 03/01/2001

Archive powered by MHonArc 2.6.19+.

Top of page