From owner-freebsd-current Wed Apr 1 18:41:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00297 for freebsd-current-outgoing; Wed, 1 Apr 1998 18:41:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00292 for ; Wed, 1 Apr 1998 18:41:51 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA09897; Wed, 1 Apr 1998 18:41:19 -0800 (PST) Message-Id: <199804020241.SAA09897@implode.root.com> To: Mikhail Teterin cc: freebsd-current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? In-reply-to: Your message of "Wed, 01 Apr 1998 21:23:08 EST." <199804020223.VAA29806@xxx.video-collage.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 01 Apr 1998 18:41:19 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >David Greenman once stated: > >= FreeBSD will slowly page infrequently used pages out in favor of >=file caching, and 8MB (or 32+8) is about what you'd expect to see in >=this case. Poul's problem seems to be different, however. > >Oh, this reminds me of something I wanted to ask. Is there a way to >control this behavior? Can I specify a limit of the file cache, for >example (with sysctl)? Or that some process is precious, and its pages >should not be swaped for file cache (without coding madvise() into >it)? The only way to do this would be to lock the pages in memory with mlock(); I don't know if the bugs have been fixed in that, however - it used to be broken. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message