> memstat isn't showing precomputed statistics (e.g.
> equivalent of a kstat
> we have stashed somewhere): the implementation of
> that dcmd is quite literally
> to iterate over every page_t in the system (1GB / 4k
> = 262144 minus a few

Right, thanks. This explains the behaviour.


> As part of the VM system reworking that is going on,
> it might be useful to
> think about having the kernel keep these things all
> the time and then we
> could modify the dcmd to simply read the cached
> values.  Rich McDougall
> and George Cameron would be the people to talk to
> about that.

I will drop them an email about this.

thanks,
Stefan

Reply via email to