From owner-freebsd-current Fri Dec 24 1:27:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B10FE15260 for ; Fri, 24 Dec 1999 01:27:24 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA29048; Fri, 24 Dec 1999 10:26:57 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Thomas David Rivers Cc: current@FreeBSD.ORG, julian@whistle.com Subject: Re: Vmware and -current In-reply-to: Your message of "Fri, 24 Dec 1999 04:20:27 EST." <199912240920.EAA76863@lakes.dignus.com> Date: Fri, 24 Dec 1999 10:26:56 +0100 Message-ID: <29046.946027616@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912240920.EAA76863@lakes.dignus.com>, Thomas David Rivers writes : >> seems to work fine, >> except that now we don't have block devices any more >> so every time it gets stuff off disk, it's REALLY SLOW. >> >> I guess a virtual machine is the "App that no-one could put their finger >> on" that really could do with buffered (caching) devices. > >Hmmm.... I wonder what it would take to bring them (block devices) back... >probably out of the question at this point... It is not out of the question to bring buffered disk access back, but it will be an ioctl enabled function for disks, not a vnode mode. Peter has suggested doing it with a layered device a'la vn(4). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message