From owner-freebsd-threads@FreeBSD.ORG Tue Jul 8 03:37:08 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 1754F37B401; Tue, 8 Jul 2003 03:37:08 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7106343F75; Tue, 8 Jul 2003 03:37:07 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc01p.dialup.mindspring.com ([209.86.0.57] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19ZpqM-0003jZ-00; Tue, 08 Jul 2003 03:37:07 -0700 Message-ID: <3F0A9E8E.99CA9BD@mindspring.com> Date: Tue, 08 Jul 2003 03:35:58 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: deischen@FreeBSD.org References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4e8e3623f1f952ee9c09b7488d51cbdd7a8438e0f32a48e08350badd9bab72f9c350badd9bab72f9c cc: threads@FreeBSD.org cc: John Baldwin 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 10:37:08 -0000 Daniel Eischen wrote: > On Mon, 7 Jul 2003, John Baldwin wrote: > > > I don't really know how to handle this. We can wrap > > > sched_get_priority_{min,max}(), but how do we know whether > > > the application wants process priorities or thread > > > priorities? > > > > Ugh. Perhaps the manpage should at least be updated to not > > reference the macros. What does POSIX say about the confusion > > between sched_get_priority_{min,max}? > > Sure, update the man pages if you want ;-) > > 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. -- Terry