public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] different proposal for mq_notify(SIGEV_THREAD)
Date: Wed, 10 Mar 2004 21:57:48 +0100	[thread overview]
Message-ID: <404F814C.1070202@colorfullife.com> (raw)
In-Reply-To: <20040310203857.GA7341@mail.shareable.org>

Jamie Lokier wrote:

>The difference is that your proposal eliminates those fds.
>But there is no reason that I can see why mq_notify() should be
>optimised in this way and futexes not.
>  
>
I would start with message queues, but the mechanism must be generic 
enough to be used for futexes, etc.

The main open question is if I should write something new or if I can 
reuse netlink.

--
    Manfred


  reply	other threads:[~2004-03-10 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07 14:05 [RFC] different proposal for mq_notify(SIGEV_THREAD) Manfred Spraul
2004-03-10 20:38 ` Jamie Lokier
2004-03-10 20:57   ` Manfred Spraul [this message]
2004-03-10 21:36     ` Jamie Lokier

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=404F814C.1070202@colorfullife.com \
    --to=manfred@colorfullife.com \
    --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