From owner-freebsd-questions Thu Nov 16 15: 9: 5 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 6249C37B4C5 for ; Thu, 16 Nov 2000 15:09:01 -0800 (PST) Received: from m415-mp1-cvx1b.gui.ntl.com ([62.252.9.159]) by mta02-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20001116230858.LOHE270.mta02-svc.ntlworld.com@m415-mp1-cvx1b.gui.ntl.com>; Thu, 16 Nov 2000 23:08:58 +0000 Date: Thu, 16 Nov 2000 23:09:17 +0000 (GMT) From: George Reid X-Sender: geeorgy@sobek.nevernet.net To: flaw Cc: freebsd-questions Subject: RE: FreeBSD VM In-Reply-To: <3A1C57B4@zathras.cc.vt.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Nov 2000, flaw wrote: > Maybe due to the amount of memory, the program is still in memory so no page > faults are induced. But why cnt.v_vm_faults (cnt is the vmmeter) are > incremented much more frequently than p->p_stats->p_ru.ru_majflt? cnt.v_vm_faults is number of page faults for the whole system (as opposed to one particular process (correct me if I'm wrong, don't have the source handy). > Also, the swapper process with pid 0 (why pid 0?) has ru_majflt the same > as cnt.v_vm_faults. Think of the swapper process as a pseudoprocess - it's part of the kernel (which controls all the VM stuff). G "And then it comes to be that the soothing light at the end of your tunnel was just a freight train, comin' your way." George Reid * greid@ukug.uk.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message