From owner-freebsd-current@FreeBSD.ORG  Sat Apr 23 03:03:02 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 8B05116A4CE; Sat, 23 Apr 2005 03:03:02 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5AB4D43D2D; Sat, 23 Apr 2005 03:03:02 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 4366872DDB; Fri, 22 Apr 2005 20:03:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id 3E81F72DD4;
	Fri, 22 Apr 2005 20:03:02 -0700 (PDT)
Date: Fri, 22 Apr 2005 20:03:02 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: David Xu <davidxu@freebsd.org>
In-Reply-To: <42678DC4.40309@freebsd.org>
Message-ID: <20050422200102.G10333@carver.gumbysoft.com>
References: <1114052573.1075.10.camel@dirk.no.domain>
	<42678DC4.40309@freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
cc: Sam Lawrance <boris@brooknet.com.au>
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: Sat, 23 Apr 2005 03:03:02 -0000

On Thu, 21 Apr 2005, David Xu wrote:

> 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.

I'm sorry, I can't parse your double negative.  On -CURRENT critical
sections (entered with critical_enter()) no longer disable interrupts, but
do inhibit preemption.  But spinlocks still do critical_enter() (see
spinlock_enter()).

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org