From owner-freebsd-threads@FreeBSD.ORG Tue Jul 8 16:41:35 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4D9737B401 for ; Tue, 8 Jul 2003 16:41:35 -0700 (PDT) Received: from mail.speakeasy.net (mail9.speakeasy.net [216.254.0.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2C7C43FCB for ; Tue, 8 Jul 2003 16:41:34 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 4719 invoked from network); 8 Jul 2003 23:41:34 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 8 Jul 2003 23:41:34 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id h68NfVGI097178; Tue, 8 Jul 2003 19:41:32 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 08 Jul 2003 19:41:45 -0400 (EDT) From: John Baldwin To: deischen@freebsd.org cc: threads@freebsd.org cc: David Xu Subject: Re: libc_r silliness X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2003 23:41:36 -0000 On 08-Jul-2003 Daniel Eischen wrote: > On Wed, 9 Jul 2003, David Xu wrote: >> >> From: "John Baldwin" >> >> > On Tuesday 08 July 2003 06:35 am, Terry Lambert wrote: >> > > Daniel Eischen wrote: >> > > > I have not found anything yet regarding sched_get_priority_{min,max} >> > > > confusion in the POSIX spec... >> > > >> > > http://www.opengroup.org/onlinepubs/007904975/functions/sched_get_priority_ >> > >max.html >> > > >> > > The functions take a policy parameter; they are supposed to >> > > return "appropriate" values, which I took to mean "appropriate >> > > to the policy parameter supplied at the time they were called": >> > > >> > > int sched_get_priority_max(int policy); >> > > int sched_get_priority_min(int policy); >> > > >> > > The sched_get_priority_max() and sched_get_priority_min() >> > > functions shall return the appropriate maximum or minimum, >> > > respectively, for the scheduling policy specified by policy. >> > >> > Yes, but in a multithreaded program when I call >> > sched_get_priority_max(SCHED_RR), does that tell me the maximum process >> > SCHED_RR priority for use with sched_setschedparam() or does it tell me the >> > maximum thread SCHED_RR priority for use with pthread_setschedparam()? >> > >> See page: >> http://www.opengroup.org/onlinepubs/007904975/basedefs/sched.h.html >> They are marked with 'TPS' code, so they are applied to thread scheduling. >> Otherwise, they should be marked with 'PS' code. > > Actually, is marked PS, not TPS, and the text of > the page talks about "process": > > Each process is controlled by an associated scheduling policy > and priority. Associated with each policy is a priority range. > Each policy definition specifies the minimum priority range for > that policy. The priority ranges for each policy may overlap > the priority ranges of other policies. > > Regardless, we have kernel scheduling parameters _and_ thread > scheduling parameters. From my interpretation, these interfaces > refer to the process scheduling, not thread scheduling. > This is a good link too: > > http://www.opengroup.org/onlinepubs/007904975/functions/xsh_chap02_08.html#tag_02_08_04_01 > > Each process shall be controlled by an associated scheduling policy > and priority. These parameters may be specified by explicit > application execution of the sched_setscheduler() or > sched_setparam() functions. > > Each thread shall be controlled by an associated scheduling policy > and priority. These parameters may be specified by explicit > application execution of the pthread_setschedparam() function. So is X/Open OSI whoever just assuming that the process and thread scheduling policies implement identical priority ranges? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/