mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Benedyczak <golbi@mat.uni.torun.pl>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] POSIX message queues - syscalls & SIGEV_THREAD
Date: Fri, 21 Nov 2003 12:40:38 +0100 (CET)	[thread overview]
Message-ID: <Pine.GSO.4.58.0311211238180.4918@ultra60> (raw)
In-Reply-To: <20031118124754.GA23333@mail.shareable.org>

On Tue, 18 Nov 2003, Jamie Lokier wrote:

[CUT]
> You are setting the first futex's word in userspace prior to the first
> futex wakeup, right?  Either 5 will detect that and return
> immediately, or it will reach 6 and the poll() returns immediately.
> No hole there.
>
> ( The async token passing flaw is that the _waker_ loses track of how
> many succesful wakeups it has sent; this is used by some
> implementations of fair semaphores, among other things.  That might be
> relevant to POSIX message queues but I do not see that it's relevant
> to the two futex problem you described. )
>

Thanks for information. I was wrongly assmuming that poll will block.
After checking the code - I know I have made a mistake.

Regards
Krzysiek

  reply	other threads:[~2003-11-21 11:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16 14:57 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 [this message]
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=Pine.GSO.4.58.0311211238180.4918@ultra60 \
    --to=golbi@mat.uni.torun.pl \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®