This sounds more like a micro benchmark tool, which is a good start, but the
real problem with VM optimizations is, that they have to take into account
real world load and especially user experience.
A simple example is the fact, that an idle desktop box will feel very sluggy
if a user comes back after a few hours break, because all visible programs
are paged out. To improve this, one could think about adding a flag to
applications like "connected to gui". This feature would need a test then,
which is no usual micro benchmark.
So I think it is a good idea to avoid to introduce slow operations in
hot code path, but it does not help much the developers in the problem of
simulating workload and measuring the interactive and real throughput.
But perhaps you can take this into account?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/