Date: Sat, 22 Oct 2005 22:24:29 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Mikhail Teterin <mi+kde@aldan.algebra.com> Cc: current@freebsd.org Subject: Re: Why page-in a SIGKILL-ed process? Message-ID: <20051022122429.GC39000@cirb503493.alcatel.com.au> In-Reply-To: <200510211100.48429@aldan> References: <200510211100.48429@aldan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2005-Oct-21 11:00:48 -0400, Mikhail Teterin 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. -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051022122429.GC39000>