From owner-freebsd-current@FreeBSD.ORG  Sat Oct 22 16:20:25 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: 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 11FCB16A41F
	for <current@freebsd.org>; Sat, 22 Oct 2005 16:20:25 +0000 (GMT)
	(envelope-from mi+kde@aldan.algebra.com)
Received: from blue.virtual-estates.net (aldan.algebra.com [216.254.65.224])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7E7FB43D45
	for <current@freebsd.org>; Sat, 22 Oct 2005 16:20:24 +0000 (GMT)
	(envelope-from mi+kde@aldan.algebra.com)
Received: from blue.virtual-estates.net (blue [127.0.0.1])
	by blue.virtual-estates.net (8.13.4/8.13.4) with ESMTP id
	j9MGKN3C039223
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 22 Oct 2005 12:20:23 -0400 (EDT)
	(envelope-from mi+kde@aldan.algebra.com)
Received: from localhost (localhost [[UNIX: localhost]])
	by blue.virtual-estates.net (8.13.4/8.13.4/Submit) id j9MGKNJc039222;
	Sat, 22 Oct 2005 12:20:23 -0400 (EDT)
	(envelope-from mi+kde@aldan.algebra.com)
X-Authentication-Warning: blue.virtual-estates.net: mi set sender to
	mi+kde@aldan.algebra.com using -f
From: Mikhail Teterin <mi+kde@aldan.algebra.com>
To: Peter Jeremy <PeterJeremy@optushome.com.au>
Date: Sat, 22 Oct 2005 12:20:22 -0400
User-Agent: KMail/1.8.2
References: <200510211100.48429@aldan>
	<20051022122429.GC39000@cirb503493.alcatel.com.au>
In-Reply-To: <20051022122429.GC39000@cirb503493.alcatel.com.au>
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVihy+z3/UR{6SCQ
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Message-Id: <200510221220.23073@aldan>
X-Mailman-Approved-At: Sun, 23 Oct 2005 11:54:37 +0000
Cc: current@freebsd.org
Subject: Re: Why page-in a SIGKILL-ed process?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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, 22 Oct 2005 16:20:25 -0000

On Saturday 22 October 2005 08:24 am, Peter Jeremy wrote:
= >17850 mi          1 -16    0  4158M  1118M wdrain 1   0:06  6.10% vim
= >
= >The question is: Why bother with paged-out parts of the process, when
= >it is already doomed by SIGKILL?

= wdrain appears to be associated with file I/O rather than paging
= (though I may be wrong here).  Is it possible that vim had started
= core-dumping before you SIGKILL'd it?  I've seen problems on other
= OS's where core-dumping processes couldn't be killed and caused
= significant performance degradation if they were very large.

Well, indeed, there was a core-dump too. The reason I thought this was
swap-related is because prior to settling on `wdrain', the process was
in `pfault' for a few moments... You are, probably, right -- it was
dumping the vim's core, when I started killing it.

As for the performance degradation during a core-dump, yes, this
definetely is not a FreeBSD-specific problem... Can't this  be
interrupted, though, by SIGKILL-ing the dying process?

Thanks!

	-mi