public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: bert hubert <bert.hubert@netherlabs.nl>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org, drepper@redhat.com, mingo@elte.hu,
	tglx@linutronix.de
Subject: Re: [patch 1/1] schedule removal of FUTEX_FD
Date: Wed, 1 Nov 2006 01:18:46 -0800	[thread overview]
Message-ID: <20061101011846.de35bd2a.akpm@osdl.org> (raw)
In-Reply-To: <20061101091135.GA22089@outpost.ds9a.nl>

On Wed, 1 Nov 2006 10:11:35 +0100
bert hubert <bert.hubert@netherlabs.nl> wrote:

> On Tue, Oct 31, 2006 at 05:23:12PM -0800, Andrew Morton wrote:
> > > Now, I realize with some dismay that simplicity is no longer a futex
> > > feature, but it might be worth considering?
> > 
> > Sure.  Perhaps we could accelerate the removal schedule if we want to do
> > this.  Let's see how many 2.6.19 users squeak first.
> 
> I must admit to never having used FUTEX_FD, but the idea of waiting on a
> FUTEX by way of epoll appealed to me. Should I resort to pipe tricks if I
> want that ability henceforth?
> 

I guess so.  Until the grand unified kernel event framework is done.

  reply	other threads:[~2006-11-01  9:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 23:09 [patch 1/1] schedule removal of FUTEX_FD akpm
2006-10-31 23:27 ` Thomas Gleixner
2006-10-31 23:48 ` Alan Cox
2006-11-01  0:05   ` Thomas Gleixner
2006-11-01  0:09   ` Andrew Morton
2006-11-01  1:19 ` Rusty Russell
2006-11-01  1:23   ` Andrew Morton
2006-11-01  9:11     ` bert hubert
2006-11-01  9:18       ` Andrew Morton [this message]
2006-11-01 10:03         ` bert hubert
2006-11-01 10:19   ` Eric Dumazet

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=20061101011846.de35bd2a.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=bert.hubert@netherlabs.nl \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    /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