From owner-cvs-all  Thu Mar 11 17:12:41 1999
Delivered-To: cvs-all@freebsd.org
Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65])
	by hub.freebsd.org (Postfix) with ESMTP
	id B2DAD15000; Thu, 11 Mar 1999 17:12:33 -0800 (PST)
	(envelope-from jonny@jonny.eng.br)
Received: (from jonny@localhost)
	by roma.coe.ufrj.br (8.8.8/8.8.8) id WAA28723;
	Thu, 11 Mar 1999 22:12:15 -0300 (EST)
	(envelope-from jonny)
From: Joao Carlos Mendes Luis <jonny@jonny.eng.br>
Message-Id: <199903120112.WAA28723@roma.coe.ufrj.br>
Subject: Re: cvs commit: src/sys/vm vm_pageout.c src/sys/ufs/mfs mfs_vfsops.c
In-Reply-To: <199903120044.QAA51293@freefall.freebsd.org> from Julian Elischer at "Mar 11, 1999  4:44: 3 pm"
To: julian@FreeBSD.ORG (Julian Elischer)
Date: Thu, 11 Mar 1999 22:12:15 -0300 (EST)
Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

#define quoting(Julian Elischer)
//   Modified files:
//     sys/vm               vm_pageout.c 
//     sys/ufs/mfs          mfs_vfsops.c 
//   Log:
//   Stop the mfs from trying to swap out crucial bits of the mfs
//   as this can lead to deadlock.

Does this change still allow mfs storage to be swapped out ?
I do not like the idea of mfs permanently using RAM memory.
If it is so, then maybe it's time to think again about tmpfs and
give a big advice to mfs users.

					Jonny

--
Joao Carlos Mendes Luis            M.Sc. Student
jonny@jonny.eng.br                 Universidade Federal do Rio de Janeiro
"This .sig is not meant to be politically correct."


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