I applied it and added some of my own statistics. Very nice, much nicer than
the traditional compile-reboot-measure-the-time cycle.
For one thing, it means you can watch the system in operation under a test
load and see what it's really doing. Chances are, you know right then
whether it's running well or not and don't have to wait till the end of a
long test run.
Problem: none of the statistics show up in proc until the first time the
kernel hits them. The /proc/stats entry isn't even there until the kernel
hits the first statistic. This isn't user-friendly.
I can see that this patch is going to break a lot between kernel updates,
because it touches precisely the places we work on all the time - that's why
the stats are there, right? I'd suggest breaking it into two patchs, one
with all the support and a few basic statistics in stable places, and another
that adds in the rest of your current favorite vm stats. It would also be
nice if the stats were broken up into sets that can be catted out of proc
onto the screen, in other words, sets of 23 or less. This would mean that
that something like watch cat /proc/stats/vm is already an effective
I already learned a lot more about the what's actually happening inside the
vm using this. One thing that surprised me is how few locked pages there
actually are on the inactive_dirty list. I suppose I'd need a heavy mmap
load to see more activity there. Maybe a heavy write load would show up more
there, but for now it looks like there are so few of those locked pages it
won't interfere with scanning performance at all.
> On the userlevel side, I got zab's cpustat nice tool and transformed it
> into an ugly hack which allows me to easily add/remove statistic
I didn't get that to work. It seemed to be looking at the wrong /proc file.
I didn't look into it further.
-- Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/