[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070422084843.GJ2986@holomorphy.com>
Date: Sun, 22 Apr 2007 01:48:43 -0700
From: William Lee Irwin III <wli@...omorphy.com>
To: Ulrich Drepper <drepper@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Kyle Moffett <mrmacman_g4@....com>, Willy Tarreau <w@....eu>,
Ingo Molnar <mingo@...e.hu>, Con Kolivas <kernel@...ivas.org>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Nick Piggin <npiggin@...e.de>, Mike Galbraith <efault@....de>,
Arjan van de Ven <arjan@...radead.org>,
Peter Williams <pwil3058@...pond.net.au>,
Thomas Gleixner <tglx@...utronix.de>, caglar@...dus.org.tr,
Gene Heskett <gene.heskett@...il.com>
Subject: Re: [REPORT] cfs-v4 vs sd-0.44
On 4/22/07, William Lee Irwin III <wli@...omorphy.com> wrote:
>> I'm just looking for what people want the API to be here. With that in
>> hand we can just go out and do whatever needs to be done.
On Sun, Apr 22, 2007 at 12:17:31AM -0700, Ulrich Drepper wrote:
> I think a sched_yield_to is one interface:
> int sched_yield_to(pid_t);
All clear on that front.
On Sun, Apr 22, 2007 at 12:17:31AM -0700, Ulrich Drepper wrote:
> For futex(), the extension is needed for the FUTEX_WAIT operation. We
> need a new operation FUTEX_WAIT_FOR or so which takes another (the
> fourth) parameter which is the PID of the target.
> For FUTEX_LOCK_PI we need no extension. The futex value is the PID of
> the current owner. This is required for the whole interface to work
> in the first place.
We'll have to send things out and see what sticks here. There seems to
be some pickiness above.
-- wli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists