From: Jamie Lokier <jamie@shareable.org>
To: Krzysztof Benedyczak <golbi@mat.uni.torun.pl>
Cc: linux-kernel@vger.kernel.org,
Manfred Spraul <manfred@colorfullife.com>,
Urlich Drepper <drepper@redhat.com>,
Michal Wronski <wrona@mat.uni.torun.pl>
Subject: Re: [PATCH] POSIX message queues - syscalls & SIGEV_THREAD
Date: Mon, 17 Nov 2003 06:48:32 +0000 [thread overview]
Message-ID: <20031117064832.GA16597@mail.shareable.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0311161546260.25475@Juliusz>
Krzysztof Benedyczak wrote:
> Intuitive
> solution is with FUTEX_FD & poll but this will have synchronization
> problems. The solution with one futex and multiple values would be very
> complicated (we need mechanism for cancellation of notification and of
> course information which queue(s) produced event(s)). On the another hand
> I can think about signals doing all the work - using thread sig mask we
> have synchronization and signals can carry quite a lot information. Of
> course this are only suggestions and I can miss something about futexes.
Please can you describe your "intuitive solution" using FUTEX_FD more clearly?
I don't quite understand what you wrote, but there are flaws(*) in the
current FUTEX_FD implementation which I would like to fix anyway.
Perhaps we can improve async futexes in a way which is useful for you?
Thanks,
-- Jamie
(*) FUTEX_FD cannot be used as a drop-in replacement for synchronous
futexes, due to a race condition in cancellation.
next prev parent reply other threads:[~2003-11-17 6:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 14:57 [PATCH] POSIX message queues - syscalls & SIGEV_THREAD Krzysztof Benedyczak
2003-11-16 15:35 ` Manfred Spraul
2003-11-17 13:57 ` Krzysztof Benedyczak
2003-11-17 6:48 ` Jamie Lokier [this message]
2003-11-17 14:58 ` Krzysztof Benedyczak
2003-11-17 15:33 ` Jamie Lokier
2003-11-17 19:18 ` Ulrich Drepper
2003-11-17 21:13 ` Jamie Lokier
2003-11-18 12:20 ` Krzysztof Benedyczak
2003-11-18 12:47 ` Jamie Lokier
2003-11-21 11:40 ` Krzysztof Benedyczak
2003-11-17 19:07 ` Ulrich Drepper
2003-11-17 21:14 ` Jamie Lokier
2003-11-17 21:30 ` Randy.Dunlap
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=20031117064832.GA16597@mail.shareable.org \
--to=jamie@shareable.org \
--cc=drepper@redhat.com \
--cc=golbi@mat.uni.torun.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=wrona@mat.uni.torun.pl \
/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