From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] tsleep / timer questions
Date: Fri, 25 Mar 2005 16:36:18 -0500 [thread overview]
Message-ID: <ee9e417a0503251336135b4a80@mail.gmail.com> (raw)
In-Reply-To: <20050325202349.GD93332@smp500.sitetronics.com>
> Another (final, less important) question: what is the general
> resolution of tsleep versus addclock0link going to be?
Ultimately tsleep and addclock0link events are both
triggered by the clock interrupt handler, so the precision
is the same. Tsleep inside a kproc is heavier weight,
but if you need lots of context then the kproc can help
out. It sounds like in your case addclock0link is the way
to go. Whichever makes your code simpler.
Russ
next prev parent reply other threads:[~2005-03-25 21:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 15:08 Fwd: [9fans] Ad link Brantley Coile
2005-03-24 15:54 ` Ronald G. Minnich
2005-03-24 21:15 ` Sam
2005-03-24 22:31 ` Ronald G. Minnich
2005-03-24 22:47 ` Russ Cox
2005-03-25 15:34 ` Brantley Coile
2005-03-26 0:00 ` geoff
2005-03-26 0:19 ` Russ Cox
2005-03-27 19:03 ` Fwd: " McLone
2005-03-25 4:39 ` geoff
2005-03-25 9:02 ` vdharani
2005-03-25 18:36 ` [9fans] tsleep / timer questions Devon H. O'Dell
2005-03-25 18:55 ` jmk
2005-03-25 20:19 ` Devon H. O'Dell
2005-03-25 18:57 ` Russ Cox
2005-03-25 20:04 ` Devon H. O'Dell
2005-03-25 20:12 ` Russ Cox
2005-03-25 20:23 ` Devon H. O'Dell
2005-03-25 21:36 ` Russ Cox [this message]
2005-03-26 8:30 ` Devon H. O'Dell
2005-03-26 8:36 ` [9fans] Kernel interface manpages Devon H. O'Dell
2005-03-26 17:45 ` Russ Cox
2005-03-26 19:56 ` Devon H. O'Dell
2005-03-26 23:03 ` vdharani
2005-03-26 0:22 ` [9fans] tsleep / timer questions vdharani
2005-03-25 8:51 ` Fwd: [9fans] Ad link vdharani
2005-03-25 15:27 ` Brantley Coile
2005-03-28 1:28 [9fans] tsleep / timer questions YAMANASHI Takeshi
2005-03-28 3:38 ` Russ Cox
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=ee9e417a0503251336135b4a80@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).