Date: Sat, 5 Mar 2005 12:56:36 +1100 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Julian Elischer <julian@elischer.org>, src-committers@FreeBSD.ORG, cvs-src@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_sig.c Message-ID: <20050305015636.GC4394@cirb503493.alcatel.com.au> In-Reply-To: <20050304234704.GA41005@VARK.MIT.EDU> References: <61ac46c154aa515a692308440dd1141d@FreeBSD.org> <422710DD.1070203@freebsd.org> <422719E0.10703@samsco.org> <42279B6D.1000005@freebsd.org> <20050304182629.GA39457@VARK.MIT.EDU> <4228AB27.3020204@samsco.org> <4228B504.7000302@elischer.org> <20050304212329.GA40395@VARK.MIT.EDU> <20050304231620.GA4394@cirb503493.alcatel.com.au> <20050304234704.GA41005@VARK.MIT.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2005-Mar-04 18:47:04 -0500, David Schultz wrote: >vm.swap_enabled *does* control kstack swapping only. Not according to it's documentation: "Enable entire process swapout". And based on a quick check of the code I can't see anything in the code path that restricts vm.swap_enabled to kstacks only. That said, the option "NO_SWAPPING" does state that it controls swapping of stack pages only but appears to implement a superset of vm.swap_enabled. ISTR that by the time the pager's done it's worst, there's not much left of a process but I thought it was more than the kstack. At the very least, the documentation for vm.swap_enabled is inconsistent with NO_SWAPPING. > What you're >thinking of, namely, paging in general, is controlled by whether >or not you have any swap devices configured. And maybe vm.disable_swapspace_pageouts -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050305015636.GC4394>