From owner-freebsd-current@FreeBSD.ORG  Thu Apr 21 11:25:52 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8FFA816A4CE
	for <freebsd-current@freebsd.org>;
	Thu, 21 Apr 2005 11:25:52 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5FFB643D53; Thu, 21 Apr 2005 11:25:52 +0000 (GMT)
	(envelope-from davidxu@freebsd.org)
Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3LBPnPa083711;
	Thu, 21 Apr 2005 11:25:51 GMT
	(envelope-from davidxu@freebsd.org)
Message-ID: <42678DC4.40309@freebsd.org>
Date: Thu, 21 Apr 2005 19:25:56 +0800
From: David Xu <davidxu@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.7.5) Gecko/20050402
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sam Lawrance <boris@brooknet.com.au>
References: <1114052573.1075.10.camel@dirk.no.domain>
In-Reply-To: <1114052573.1075.10.camel@dirk.no.domain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
Subject: Re: kern/78474 for 5.4? (kernel stack swapout problem again)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2005 11:25:52 -0000

Sam Lawrance wrote:

>Will this problem:
>
>Swapped out procs not brought in immediately after child exits
>http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/78474
>
>be dealt with for the release of 5.4?
>
>Perhaps I'm the only FreeBSD user with swapped out processes ;-)
>
>-Sam
>
>
>  
>

I have noticed that current spinlock implementation no longer means
that CPU must be in critical region (critical_enter is called),  even 
previous
hack TDP_WAKEPROC0 is no longer correct, :(, I think it is the time
to disable swapout.

David Xu