public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Krzysztof Benedyczak <golbi@mat.uni.torun.pl>
Cc: Jamie Lokier <jamie@shareable.org>,
	linux-kernel@vger.kernel.org,
	Manfred Spraul <manfred@colorfullife.com>,
	Michal Wronski <wrona@mat.uni.torun.pl>
Subject: Re: [PATCH] POSIX message queues - syscalls & SIGEV_THREAD
Date: Mon, 17 Nov 2003 11:07:00 -0800	[thread overview]
Message-ID: <3FB91C54.5020905@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0311171236420.29330@Juliusz>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Krzysztof Benedyczak wrote:
> In userspace we can assign one futex to
> every such a queue and pass it to kernel in mq_notify syscall. Then we can
> use FUTEX_FD to get file descriptors of all futexes and wait on them with
> poll(). On the kernel side it notification have to be triggered we change
> futex value and do FUTEX_WAKE.

Yes, this would be possible if FUTEX_FD wouldn't be useless as it is
implemented today (see the futex paper I announced here recently).  The
thing which makes FUTEX_WAIT work is the current value of the futex
which is passed to the kernel and based on which the userlevel code made
it decisions.  This part doesn't exist in case of using FUTEX_FD.


The main recent I suggested using futexes for the notification is that
it is flexible.  For now, we can use simple waiting by creating the
thread ahead of time.  This could change later when there is a reliable
multi-futex wait operation.

- -- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/uRxU2ijCOnn/RHQRArcGAJ921MfetyPy1ciyYE2C7SG6nm0RLQCfbbwh
AUFbyDBmQJGAd1Vk+20TaTc=
=o+cD
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2003-11-17 19:07 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
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 [this message]
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=3FB91C54.5020905@redhat.com \
    --to=drepper@redhat.com \
    --cc=golbi@mat.uni.torun.pl \
    --cc=jamie@shareable.org \
    --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