On Fri, Oct 29, 1999 at 02:47:43PM -0500, Alan Cox wrote:
> I would appreciate it if people running -current would run a "vmstat -s"
> and tell me if they see a NON-ZERO value for copy-on-write optimized
> faults. About six months ago, I implemented a simpler and more general
> optimization at an earlier "fork in the road". (In effect, I avoid
> the creation of the redundant vm object that "copy-on-write
> optimized faults" applies to.)
>
> If I don't hear anything, I plan to remove the vestiges of this
> "optimization" from the vm fault handler.
Those "about six months" can you be more specific ?
$ uname -a
FreeBSD pebbles.tele.dk 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Thu Apr 22 11:52:50 CEST
1999
[EMAIL PROTECTED]:/usr/src/sys/compile/PEBBLES i386
$ vmstat -s
242909040 cpu context switches
1764534458 device interrupts
151630026 software interrupts
361271052 traps
802782672 system calls
229776 swap pager pageins
355954 swap pager pages paged in
121084 swap pager pageouts
252874 swap pager pages paged out
14474579 vnode pager pageins
34770101 vnode pager pages paged in
0 vnode pager pageouts
0 vnode pager pages paged out
105178 page daemon wakeups
104901019 pages examined by the page daemon
404278 pages reactivated
3711393 copy-on-write faults
199653 copy-on-write optimized faults
69735710 zero fill pages zeroed
11909269 zero fill pages prezeroed
253956 intransit blocking page faults
198695719 total VM faults taken
170612522 pages freed
20 pages freed by daemon
6212764 pages freed by exiting processes
11845 pages active
3420 pages inactive
1289 pages in VM cache
6865 pages wired down
144 pages free
4096 bytes per page
469466776 total name lookups
cache hits (87% pos + 0% neg) system 2% per-directory
deletions 0%, falsehits 0%, toolong 0%
/Jesper
--
Jesper Skriver (JS4261-RIPE), Network manager
Tele Danmark DataNet, IP section (AS3292)
One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
