From owner-freebsd-threads@FreeBSD.ORG  Tue Apr 15 23:22:14 2003
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 48C0637B401
	for <threads@freebsd.org>; Tue, 15 Apr 2003 23:22:14 -0700 (PDT)
Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 880DA43F85
	for <threads@freebsd.org>; Tue, 15 Apr 2003 23:22:13 -0700 (PDT)
	(envelope-from jroberson@chesapeake.net)
Received: from localhost (jroberson@localhost)
	by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h3G6MDr83201
	for <threads@freebsd.org>; Wed, 16 Apr 2003 02:22:13 -0400 (EDT)
	(envelope-from jroberson@chesapeake.net)
Date: Wed, 16 Apr 2003 02:22:12 -0400 (EDT)
From: Jeff Roberson <jroberson@chesapeake.net>
To: threads@freebsd.org
Message-ID: <20030416021527.J76635-100000@mail.chesapeake.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: struct proc
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2003 06:22:14 -0000

p_maxthrwaits should go away.  It is ok to do the wakeup everytime you
transition from p_numthreads == max_threads_per_proc to p_numthreads ==
max_threads_per_proc - 1.

p_profthreads also seems like overkill but I don't have anything to
suggest at the moment.