From owner-freebsd-bugs  Fri May  8 21:13:40 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA18835
          for freebsd-bugs-outgoing; Fri, 8 May 1998 21:13:40 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from flea.best.net (root@flea.best.net [206.184.139.131])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18824;
          Fri, 8 May 1998 21:13:34 -0700 (PDT)
          (envelope-from dillon@flea.best.net)
Received: (from dillon@localhost) by flea.best.net (8.8.8/8.7.3) id VAA10624; Fri, 8 May 1998 21:12:48 -0700 (PDT)
Date: Fri, 8 May 1998 21:12:48 -0700 (PDT)
From: Matt Dillon <dillon@best.net>
Message-Id: <199805090412.VAA10624@flea.best.net>
To: Poul-Henning Kamp <phk@FreeBSD.ORG>
Cc: phk@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/5197
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

:
:Synopsis: The swapper is ineffective
:
:State-Changed-From-To: open-closed
:State-Changed-By: phk
:State-Changed-When: Fri May 8 13:45:05 PDT 1998
:State-Changed-Why: 
:Doing what you suggest would prevent the swapper from acting as
:last defense against low-mem conditions.  I belive the future of
:the swapper is generally uncertain with a tendency to "kill it!"
:being mumbled.  (Look for NO_SWAPPING in the -current vmcode).

    I think the -2.2.x and -current trees already have the 
    swap-out-code-sleeping-over-N-seconds committed, so even
    though you completely misunderstood the PR, the bug
    report should be closed for other reasons anyway.

					-Matt

    Matthew Dillon   Engineering, BEST Internet Communications, Inc.
		    <dillon@best.net>
    [always include a portion of the original email in any response!]

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message