From owner-freebsd-current Thu Jun 7 1:52:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fxp0.halvsten.ip.cybercity.dk [212.242.40.114]) by hub.freebsd.org (Postfix) with ESMTP id A4A3A37B401 for ; Thu, 7 Jun 2001 01:52:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f576uR190994; Thu, 7 Jun 2001 08:56:27 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mikhail Teterin Cc: current@freebsd.org Subject: Re: mdconfig and _virtual_ memory In-Reply-To: Your message of "Wed, 06 Jun 2001 10:19:34 EDT." <200106061419.f56EJYN18798@aldan.algebra.com> Date: Thu, 07 Jun 2001 08:56:27 +0200 Message-ID: <90992.991896987@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200106061419.f56EJYN18798@aldan.algebra.com>, Mikhail Teterin write s: >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. The swap backing in md(4) is a straight copy of the code which lived in vn(4). I'm not terribly familiar with that code, but I would expect that it would work with no swap space as well. Your man is probably Matt Dillon... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message