From owner-freebsd-emulation Wed Feb 14 8: 6:34 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 567E437B401 for ; Wed, 14 Feb 2001 08:06:28 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA25211; Wed, 14 Feb 2001 11:06:23 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f1EG5et52577; Wed, 14 Feb 2001 11:05:40 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14986.44244.784506.737009@grasshopper.cs.duke.edu> Date: Wed, 14 Feb 2001 11:05:40 -0500 (EST) To: Matt Dillon Cc: freebsd-emulation@FreeBSD.ORG, vsilyaev@mindspring.com Subject: Re: What's changed recently with vmware/linuxemu/file I/O In-Reply-To: <200102131717.f1DHHa373170@earth.backplane.com> References: <14980.8856.555504.633075@grasshopper.cs.duke.edu> <14980.48507.507487.690557@grasshopper.cs.duke.edu> <200102100616.f1A6GCf21887@earth.backplane.com> <3A896B57.DF61F266@Lustig.COM> <200102131717.f1DHHa373170@earth.backplane.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matt Dillon writes: > > : > :Matt Dillon wrote: > :> As far as I know vmware is not wiring pages down. > :> > : > :Actually, when vmware starts the number of wired pages, according to > :systat, jumps significantly. > : > :barry > > That doesn't mean VMWare is wiring them down, it simply means that > the pages have been mapped and accessed by the process. Pages referenced > by page tables are always wired in the system, but the wiring is > temporary. > > -Matt I think that VMware is wiring them down. I'm sure I have heard Vladimir Silyaev mention it & host_lock_ppn() in VMware's kernel module is apparently calling vm_page_wire(). Hmm.. it should probably also be setting the PG_NOSYNC bit itself, so as to avoid most of this mess.. Speaking of PG_NOSYNC, did you happen to see my message earlier in this thread (when it was on -hackers) regarding MAP_NOSYNC not working properly when the first fault is a read fault? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message