Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 1 Jul 2002 02:46:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 1 Jul 2002 02:46:27 -0400 Received: from ns.suse.de ([213.95.15.193]:28676 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id ; Mon, 1 Jul 2002 02:46:26 -0400 To: Nicholas Miell Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Linus Torvalds Subject: Re: [announce] [patch] batch/idle priority scheduling, SCHED_BATCH References: <1025492120.12685.8.camel@entropy> From: Andreas Jaeger Date: Mon, 01 Jul 2002 08:48:51 +0200 In-Reply-To: <1025492120.12685.8.camel@entropy> (Nicholas Miell's message of "30 Jun 2002 19:55:18 -0700") Message-ID: User-Agent: Gnus/5.090007 (Oort Gnus v0.07) XEmacs/21.4 (Artificial Intelligence, i386-suse-linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1150 Lines: 27 Nicholas Miell writes: > On Sun, 2002-06-30 at 17:26, Ingo Molnar wrote: > >> -#define SCHED_OTHER 0 >> +#define SCHED_NORMAL 0 > >>From IEEE 1003.1-2001 / Open Group Base Spec. Issue 6: > "Conforming implementations shall include one scheduling policy > identified as SCHED_OTHER (which may execute identically with either the > FIFO or round robin scheduling policy)." > > So, you probably want to add a "#define SCHED_OTHER SCHED_NORMAL" here > in order to prevent future confusion, especially because the user-space > headers have SCHED_OTHER, but no SCHED_NORMAL. This can be done in glibc. linux/sched.h should not be used by userspace applications, glibc has the define in which is included from - and is the file defined by Posix. Andreas -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj - 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/