From owner-cvs-src@FreeBSD.ORG  Sat May  8 07:38:09 2004
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3263116A4CE; Sat,  8 May 2004 07:38:09 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9533A43D54; Sat,  8 May 2004 07:38:08 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i48Ec7Oa012996;
	Sat, 8 May 2004 10:38:07 -0400 (EDT)
Date: Sat, 8 May 2004 10:38:07 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Julian Elischer <julian@FreeBSD.org>
In-Reply-To: <200405080856.i488u6DU019660@repoman.freebsd.org>
Message-ID: <Pine.GSO.4.10.10405081034560.11288-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: cvs-src@FreeBSD.org
cc: src-committers@FreeBSD.org
cc: cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/sys/kern kern_resource.c
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 08 May 2004 14:38:09 -0000

On Sat, 8 May 2004, Julian Elischer wrote:

> julian      2004/05/08 01:56:05 PDT
> 
>   FreeBSD src repository
> 
>   Modified files:
>     sys/kern             kern_resource.c 
>   Log:
>   Fix rtprio() to do sensible things when called from threaded processes.
>   It's not quite correct from a posix Point Of view, but it is a lot better
>   than what was there before. This will be revisited later
>   when we decide what form our priority extensions will take. Posix doesn't
>   specify  how a system scope thread can change its priority so you need to
>   add non-standard extensions to be able to do it..
>   For now make this slightly non standard to allow it to be done.

rtprio() isn't in the standard, so you can make it have
any behavior you want.  It's only nice() and sched_setparam()
that operate on the process as a whole.

-- 
Dan Eischen