Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 18 Jun 2002 14:51:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 18 Jun 2002 14:51:48 -0400 Received: from pixpat.austin.ibm.com ([192.35.232.241]:25307 "EHLO wagner.rustcorp.com.au") by vger.kernel.org with ESMTP id ; Tue, 18 Jun 2002 14:51:48 -0400 Date: Wed, 19 Jun 2002 04:56:06 +1000 From: Rusty Russell To: David Schwartz Cc: mgix@mgix.com, linux-kernel@vger.kernel.org Subject: Re: Question about sched_yield() Message-Id: <20020619045606.3566a8cc.rusty@rustcorp.com.au> In-Reply-To: <20020618004630.AAA28082@shell.webmaster.com@whenever> References: <20020618004630.AAA28082@shell.webmaster.com@whenever> X-Mailer: Sylpheed version 0.7.4 (GTK+ 1.2.10; powerpc-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 723 Lines: 18 On Mon, 17 Jun 2002 17:46:29 -0700 David Schwartz wrote: > "The sched_yield() function shall force the running thread to relinquish the > processor until it again becomes the head of its thread list. It takes no > arguments." Notice how incredibly useless this definition is. It's even defined in terms of UP. Rusty. -- there are those who do and those who hang on and you don't see too many doers quoting their contemporaries. -- Larry McVoy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/