From: DervishD <raul@pleyades.net>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Tom Sanders <developer_linux@yahoo.com>,
redhat-list@redhat.com, linux-kernel@vger.kernel.org,
redhat-devel-list@redhat.com
Subject: Re: Linux application level timers?
Date: Thu, 23 Jan 2003 18:26:50 +0100 [thread overview]
Message-ID: <20030123172650.GA104@DervishD> (raw)
In-Reply-To: <3E301833.8030103@nortelnetworks.com>
Hi Chris and Tom :))
> >Which Linux timer facility can be used for this?
> I used setitimer for a similar task. Since you can only have one timer
> going at any given time, I set up a linked list of timing events, with
> each event's timeout expressed as a delta from the previous event.
Tom, if you're interested, I coded a timer multiplexor for Linux
(user space, I mean) a time ago, and although it hasn't been released
yet, has been in use for a year in The Puto Amo Window Manager, so I
think it is pretty stable. It's GPL'd, but not released yet because
it lacks documentation by now and I want to change a couple of
things.
If you want, I can attach you the code (is pretty simple), or
even better, you can go to www.pleyades.net/~pawm, download the
window manager and pick the code from there (is a bit more updated
that mine, since has a couple of contributions). The file is called
timux.[c,h], and needs too the file chain.c for the data container.
Just let me know. And count on any help you need with TiMux ;))
Raúl
prev parent reply other threads:[~2003-01-23 17:17 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
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 [this message]
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=20030123172650.GA104@DervishD \
--to=raul@pleyades.net \
--cc=cfriesen@nortelnetworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox