From: george anzinger <george@mvista.com>
To: Tom Sanders <developer_linux@yahoo.com>
Cc: redhat-list@redhat.com, linux-kernel@vger.kernel.org,
redhat-devel-list@redhat.com
Subject: Re: Linux application level timers?
Date: Wed, 22 Jan 2003 15:35:39 -0800 [thread overview]
Message-ID: <3E2F2ACB.E74DEFBC@mvista.com> (raw)
In-Reply-To: 20030122221703.42913.qmail@web9806.mail.yahoo.com
Tom Sanders wrote:
>
> I'm writing an application server which receives
> requests from other applications. For each request
> received, I want to start a timer so that I can fail
> the application request if it could not be completed
> in max specified time.
>
> Which Linux timer facility can be used for this?
>
> I have checked out alarm() and signal() system calls,
> but these calls doesn't take an argument, so its not
> possible to associate application request with the
> matured alarm.
Sounds like a job for POSIX clocks & timers. See here:
http://sourceforge.net/projects/high-res-timers/
-g
>
> Any inputs?
>
> Thanks in advance,
> Tom
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2003-01-22 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 22:17 Linux application level timers? Tom Sanders
2003-01-22 23:03 ` Steven Dake
2003-01-22 23:35 ` george anzinger [this message]
2003-01-23 4:36 ` Gerhard Mack
2003-01-23 8:37 ` Narsimha Reddy CH
2003-01-23 8:51 ` Riku Meskanen
2003-01-23 16:28 ` Chris Friesen
2003-01-23 17:26 ` DervishD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E2F2ACB.E74DEFBC@mvista.com \
--to=george@mvista.com \
--cc=developer_linux@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=redhat-devel-list@redhat.com \
--cc=redhat-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.