RE: Linux timers

["Saravanan" <psaravanan@xxxxxxxxxxxxxxxxxxxxxxxx>]

Hello Yaniv,

    My two cents ... I work on an application that needs timers ... these timers need not timeout at the exact milli/microsecond but need to timeout at reasonable time intervals. So we implemented a timers mechanism that is internal to the application. These timers are decremented based on a function call that is called every once in a while by the application main thread. Once the timer reaches zero, the function associated with the timer is called. These function could be just plain c functions or could be more complex C++ member functions (based on the way the timers are implemented) ... Though my application is single threaded, this kind of timer implementation allows me to time slice for each module in my application. Therefore if one module take forever to come out of the timer function, it holds up the timer mechanism. You could be more adventurous and try a multi threaded implementation.

 

regards

Saravanan

-----Original Message-----
From: redhat-devel-list-bounces@xxxxxxxxxx [mailto:redhat-devel-list-bounces@xxxxxxxxxx]On Behalf Of Yaniv Weizman
Sent: Sunday, October 10, 2004 3:27 AM
To: redhat-devel-list@xxxxxxxxxx
Cc: Niv; Alon
Subject: Linux timers

Hello,

We are developing high load application which handles thousands of transactions.

For each user transaction we should set a low resolution (seconds) timer for transaction maintenance – means lot of kernel concurrent timers.

Can we simply use the Linux kernel timer system without overload the kernel performance, or we should set our own timer wheel mechanism for handling such a big number of timers?

Regards,

Yaniv.    

 

Weizman Yaniv

Communication Senior Engineer

(Tel: +972-3-6349990 ext. 211

ÊFax: +972-3-6349910

ÈCellular: +972-54-8100088

E-mail: yaniv@xxxxxxxxxxxxxm

 

_______________________________________________
Redhat-devel-list mailing list
Redhat-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/redhat-devel-list