> 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.)
>
FreeBSD ns.internet.dk 3.3-STABLE FreeBSD 3.3-STABLE #6: Fri Oct 1 16:06:46 CEST 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/DK i386
0 swap pager pageins
0 swap pager pages paged in
0 swap pager pageouts
0 swap pager pages paged out
15535 vnode pager pageins
36906 vnode pager pages paged in
1 vnode pager pageouts
1 vnode pager pages paged out
288 page daemon wakeups
443092 pages examined by the page daemon
3784 pages reactivated
9272885 copy-on-write faults
2062637 copy-on-write optimized faults <<????????????
16279599 zero fill pages zeroed
13314568 zero fill pages prezeroed
331 intransit blocking page faults
30579022 total VM faults taken
32474529 pages freed
268 pages freed by daemon
20062301 pages freed by exiting processes
19657 pages active
34300 pages inactive
1952 pages in VM cache
7255 pages wired down
800 pages free
4096 bytes per page
54787453 total name lookups
cache hits (77% pos + 7% neg) system 4% per-directory
deletions 0%, falsehits 0%, toolong 0%
I must have something configured wrong, or???
Leif
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
