From owner-freebsd-current Wed Jun 6 7:19: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by hub.freebsd.org (Postfix) with ESMTP id 804CA37B401; Wed, 6 Jun 2001 07:18:58 -0700 (PDT) (envelope-from mi@aldan.algebra.com) Received: (from mi@localhost) by aldan.algebra.com (8.11.3/8.11.4) id f56EJYN18798; Wed, 6 Jun 2001 10:19:34 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <200106061419.f56EJYN18798@aldan.algebra.com> Subject: mdconfig and _virtual_ memory To: current@freebsd.org Date: Wed, 6 Jun 2001 10:19:34 -0400 (EDT) Cc: phk@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! For years of using MFS I presumed, that it used virtual memory -- RAM and swap to store the file system -- using RAM for speed of MFS and swap when RAM was needed by others. When I moved to mdconfig, I figured I have to use ``-t swap'' for the same effect, but it seems, I was wrong -- apparently, ``swap'' means the filesystem will always hit the disk, even if there is plenty of RAM to go around. My suspicion was further confirmed, by disabling the swapping at all -- the mdconfig-ed device stopped working -- disklabel got ENOMEM. Now I use ``-t malloc'', but I suspect, this will never hit the disk, even if there is where to swap and more memory can be used elsewhere. It seems, ``-t malloc'' simply bites a chunk of RAM away... Is it possible to make md-devices backed by _virtual memory_? Did the old MFS do that? Where else am I wrong in this letter? Thanks! Yours, -mi P.S. Where is that new mount_mfs wrapper? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message