From owner-freebsd-emulation Thu Feb 1 19: 7:53 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 37D1A37B65D; Thu, 1 Feb 2001 19:07:34 -0800 (PST) Received: from delta.rc.ny.us (nyf-ny3-29.ix.netcom.com [198.211.16.157]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id WAA14652; Thu, 1 Feb 2001 22:07:31 -0500 (EST) Received: (from vsilyaev@localhost) by delta.rc.ny.us (8.11.1/8.9.3) id f1237Tn00673; Thu, 1 Feb 2001 22:07:29 -0500 (EST) (envelope-from vsilyaev) Date: Thu, 1 Feb 2001 22:07:28 -0500 From: Vladimir Silyaev To: Robert Watson Cc: emulation@FreeBSD.org, mdillon@FreeBSD.org Subject: Re: long hangs running vmware -- vm system interactions? Message-ID: <20010201220728.A653@delta.rc.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >/var/tmp (or where-ever), mmap'ing it, and then touching the pages. I'm >not sure what the sequence of events for creating the file is, but one >suspects they seek to create a sparse file, and then the touching of pages >causes the pages/blocks to be allocated sequentially. It just create file, mmaped it, unlink it and seek at the end. The big difference with comparsion with normal operation, that vmware mmaped pages are not just touching, but also being 'wired'. Just my five cents ;) -- Vladimir P.S. You shouldn't run/connect rtc if you are not really need it. It just eating CPU as a dog. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message