From: Nigel Gamble <nigel@nrg.org>
To: Daniel Phillips <phillips@innominate.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Semaphores used for daemon wakeup
Date: Mon, 18 Dec 2000 16:14:56 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.05.10012181611430.2088-100000@cosmic.nrg.org> (raw)
In-Reply-To: <0012171922570J.00623@gimli>
On Sun, 17 Dec 2000, Daniel Phillips wrote:
> This patch illustrates an alternative approach to waking and waiting on
> daemons using semaphores instead of direct operations on wait queues.
> The idea of using semaphores to regulate the cycling of a daemon was
> suggested to me by Arjan Vos. The basic idea is simple: on each cycle
> a daemon down's a semaphore, and is reactivated when some other task
> up's the semaphore.
> Is this better, worse, or lateral?
This is much better, especially from a maintainability point of view.
It is also the method that a lot of operating systems already use.
Nigel Gamble nigel@nrg.org
Mountain View, CA, USA. http://www.nrg.org/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-19 0:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-17 12:06 [RFC] Semaphores used for daemon wakeup Daniel Phillips
2000-12-19 0:14 ` Nigel Gamble [this message]
2000-12-19 3:34 ` Tim Wright
2000-12-19 13:11 ` Daniel Phillips
2000-12-19 16:07 ` Tim Wright
2000-12-20 1:34 ` Daniel Phillips
2000-12-21 16:28 ` Tim Wright
2000-12-19 9:01 ` Daniel Phillips
[not found] <3A42380B.6E9291D1@sgi.com>
2000-12-21 19:30 ` Paul Cassella
2000-12-21 22:19 ` Tim Wright
2000-12-22 1:12 ` Daniel Phillips
2000-12-22 1:50 ` Daniel Phillips
2000-12-22 4:26 ` Paul Cassella
2000-12-22 11:46 ` Daniel Phillips
2000-12-22 15:33 ` Tim Wright
2000-12-22 17:25 ` Daniel Phillips
2000-12-22 17:32 ` Brian Pomerantz
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=Pine.LNX.4.05.10012181611430.2088-100000@cosmic.nrg.org \
--to=nigel@nrg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@innominate.de \
/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).