From: "Banu R Reefath" <reefathbanur@myw.ltindia.com>
To: <linux-kernel@vger.kernel.org>
Subject: Timers to threads
Date: Thu, 31 Mar 2005 11:52:04 +0530 [thread overview]
Message-ID: <s24be47e.095@EMAIL> (raw)
Dear Sir/Mam
We are using Linux in one of our embedded products.This is the first time we are working in this Platform.We have few doubts regarding implementing s/w timers & how to pass the timer interrupts to threads .
In net we coudnt find exactly what we want .Could you please help us in this regard?
Ideas from us
1. If we want a thread to execute at particular intervals should it be done only through
usleep() system call ? Will it be accurate enough ?
Because it is a real time design for a Medical Product.
2. If we use kernel timers to invoke at particular time intervals using add_timer () how to pass on to the application that the time has elapsed?
A piece of code demonstartion would be much more helpful to us
Thanks & Regards,
Reefath Banu Rajali
Software Engineer
Larsen & Toubro
Embedded Systems & Software
Mysore
India
next reply other threads:[~2005-03-31 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 6:22 Banu R Reefath [this message]
2005-03-31 11:28 ` Timers to threads lk
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=s24be47e.095@EMAIL \
--to=reefathbanur@myw.ltindia.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox