I suggest you to look at POSIX's timer_create() and related functions. If you want your handlers to run in parrallel, just use one distinct SIGEV_THREAD per timer. No need to use any signals here.
On Mon, Feb 2, 2009 at 3:46 AM, Girish <[email protected]> wrote: > > David, > > Thanks, > > How should the problem be resoloved in our case ? SIGRTMIN and > SIGRTMAX was available in the previous port of middleware application > and it was a difference of 32 between.So per process we were able to > create at the max of 32 timers for our middleware C application.. > (SIGRTMAX-SIGRTMIN = 32) > > I hope you can understand the scenario, Is there anyways to use a > single user space (SIGUSR1) signal to hanldle multiple timers in > parallel ? Is there anything like soft timers ? Can you give us some > clues ? > > Regards > Girish > > On Feb 2, 7:33 am, David Turner <[email protected]> wrote: > > the cupcake C library already supports real-time timers through > > timer_create(). > > real-time signals are a different thing and they are not currently > > supported. > > > > For the record, with other C libraries, not all of SIGRTMIN .. SIGRTMAX > is > > available to application-defined purposes. > > The implementation usually reserves a few signals for its own use. Which > one > > exactly depends on the C library you're > > using, so things aren't exactly too portable here. > > > > On Sun, Feb 1, 2009 at 5:14 PM, Girish <[email protected]> wrote: > > > > > Hi David, > > > > > Will there be any support for POSIX RT timers in near future. As the > > > application needs more than 20 timers. In POSIX it was achievable > > > because of the fact that it was supporting SIGRTMIN to SIGRTMAX, are a > > > set of signals that can be used for application-defined purposes. > > > > > > Or using one thread per timer, each one simply doing a timed wait ? > > > For now please explain us how to develop timer functionality in > > > parallel. > > > > > Regards > > > Girish > > > > > On Feb 1, 8:26 am, David Turner <[email protected]> wrote: > > > > Maybe by using a single signal with a sorted timer queue ? > > > > Or using one thread per timer, each one simply doing a timed wait ? > > > > > > Any code that requires 25 signals is not going to work, on any > platform > > > > > > On Fri, Jan 30, 2009 at 1:16 AM, kd.itbhu <[email protected]> > wrote: > > > > > > > Hi; > > > > > I need around 25 times which can run simultaneously. > > > > > But we have two type singnals ISGUSR1 and SIGUSR2. > > > > > So only two timers can run simultaneously. > > > > > > > Do we have anyother way to run more than 2 timers simultaneously. > > > > > > > Please help me rregarding it. > > > > > > > Thanks in advance > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
