[Bug tapsets/6457] Provide I/O traces for iogrind

[michael dot meeks at novell dot com]

------- Additional Comments From michael dot meeks at novell dot com  2008-04-25 12:02 -------
This would be cool. One of the (two) biggest problems with iogrind currently is
that it requires running valgrind on the application to collect it's data: this
makes it incredibly slow - and difficult to use for complicated scenarios.

What I'd like is something fast we can use to generate a trace for a whole
system install - such that, we can subsequently re-run the install through a
cut-down kernel very quickly with a tweaked file-system layout algorithm, and
see what effect that has on various common operations. ie. real, repeatable,
wide-scale performance regression testing for kernel file-systems.

What I really need to see (beyond what strace can show (ie. all I/O relevant
syscalls)) is first touches of memory mapped pages: both reads and writes.

Would be wonderful if we could have that.

There is an existing (somewhat lame) logging syntax used in iogrind, seen in the
tests/ directory - but that's easy to tweak later: I just need the know-how to
create the hooks.

Thanks.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=6457

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.