From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754138AbXDVHRd (ORCPT ); Sun, 22 Apr 2007 03:17:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754140AbXDVHRc (ORCPT ); Sun, 22 Apr 2007 03:17:32 -0400 Received: from nz-out-0506.google.com ([64.233.162.226]:18465 "EHLO nz-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754138AbXDVHRc (ORCPT ); Sun, 22 Apr 2007 03:17:32 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AQf8T8/lk4Ntd5oXcFFXkFXOze7ts/gZh3idzQACwsA33UKwCO0hkVQNSCucwgBDfWrP3XJmD6s9Vr9PdNNaS0pL9tZVIOCHvto4tSnOilY3tV6Ayiu4APezZVrynGm409I3X2ERDRgAknsW8FkQaF/vXaLaJY6Vx8tt7OyspdI= Message-ID: Date: Sun, 22 Apr 2007 00:17:31 -0700 From: "Ulrich Drepper" To: "William Lee Irwin III" Subject: Re: [REPORT] cfs-v4 vs sd-0.44 Cc: "Linus Torvalds" , "Kyle Moffett" , "Willy Tarreau" , "Ingo Molnar" , "Con Kolivas" , linux-kernel@vger.kernel.org, "Andrew Morton" , "Nick Piggin" , "Mike Galbraith" , "Arjan van de Ven" , "Peter Williams" , "Thomas Gleixner" , caglar@pardus.org.tr, "Gene Heskett" In-Reply-To: <20070422070238.GH2986@holomorphy.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070420140457.GA14017@elte.hu> <20070421154614.GA26169@elte.hu> <20070421161818.GC7840@1wt.eu> <20070421164241.GF2986@holomorphy.com> <20070422070238.GH2986@holomorphy.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 4/22/07, William Lee Irwin III 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. I think a sched_yield_to is one interface: int sched_yield_to(pid_t); 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.