From: Robert Hancock <hancockr@shaw.ca>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Theodore Tso <tytso@mit.edu>,
Neil Horman <nhorman@tuxdriver.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Dave Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org, a.zummo@towertech.it,
jg@freedesktop.org
Subject: Re: A better interface, perhaps: a timed signal flag
Date: Sat, 29 Jul 2006 12:29:46 -0600 [thread overview]
Message-ID: <44CBA91A.5030704@shaw.ca> (raw)
In-Reply-To: <fa.7gpoVg9wmtQ0g4u4T8FaCZGXup0@ifi.uio.no>
Steven Rostedt wrote:
> There's also something else that would be a nice addition to the kernel
> API. A sleep and wakeup that is implemented without signals. Similar to
> what the kernel does with wake_up. That way you can sleep till another
> process/thread is done with what it was doing and wake up the other task
> when done, without the use of signals. Or is there something that
> already does this?
For between threads, this is what the POSIX pthread API is for
(pthread_cond_wait and friends) which is implemented using futexes these
days..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-07-29 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.xkoDc6Uvpcp6dnG8+9iwy53PPeo@ifi.uio.no>
[not found] ` <fa.7gpoVg9wmtQ0g4u4T8FaCZGXup0@ifi.uio.no>
2006-07-29 18:29 ` Robert Hancock [this message]
2006-07-29 6:56 A better interface, perhaps: a timed signal flag linux
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 15:15 Brown, Len
2006-07-25 19:47 [PATCH] RTC: Add mmap method to rtc character driver Neil Horman
2006-07-25 20:04 ` Dave Airlie
2006-07-25 20:24 ` H. Peter Anvin
2006-07-25 20:47 ` Neil Horman
2006-07-25 20:50 ` H. Peter Anvin
2006-07-25 22:25 ` Neil Horman
2006-07-25 23:29 ` Segher Boessenkool
2006-07-25 23:56 ` Neil Horman
2006-07-26 0:02 ` H. Peter Anvin
2006-07-26 0:20 ` Neil Horman
2006-07-26 14:45 ` A better interface, perhaps: a timed signal flag Theodore Tso
2006-07-28 13:33 ` Steven Rostedt
2006-07-28 14:52 ` Theodore Tso
2006-07-28 15:05 ` Steven Rostedt
2006-07-28 16:41 ` Alan Cox
2006-07-28 16:44 ` Steven Rostedt
2006-07-28 20:01 ` Alan Cox
2006-07-28 20:12 ` Steven Rostedt
2006-07-28 20:36 ` Alan Cox
2006-07-28 20:31 ` Steven Rostedt
2006-07-28 17:11 ` H. Peter Anvin
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=44CBA91A.5030704@shaw.ca \
--to=hancockr@shaw.ca \
--cc=a.zummo@towertech.it \
--cc=airlied@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=jg@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=rostedt@goodmis.org \
--cc=segher@kernel.crashing.org \
--cc=tytso@mit.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 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.