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

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

[wcohen at redhat dot com]

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

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wcohen at redhat dot com

--- Comment #4 from William Cohen <wcohen at redhat dot com> 2011-10-10 14:29:47 UTC ---
I was able to get iogrind running on Fedora 15 using the git repo:

http://www.gnome.org/~michael/git/iogrind.git

The last change to iogrind was in March 2010; there doesn't seem to be much
activity on it. iogrind needs various mono packages to build and run including
(available in Fedora, but not in RHEL6):

gtk-sharp2-devel


Able to get plots from the examples in the tests directory. However, things
seem pretty fragile. Get lots of output like the following:

ARGH - broken sect numbers in 'scribble' need fixing
ARGH - broken sect numbers in 'scribble' need fixing
ARGH - broken sect numbers in 'scribble' need fixing

And iogrind crashes when switched to the scribble mode.

The main point of getting a local version of iogrind working is to be able to
tests out any output from a systemtap script.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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

[gobisha6355 at gmail dot com]

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

shanjay <gobisha6355 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW
          Component|tapsets                     |core
           Assignee|systemtap at sourceware dot org    |unassigned at sourceware dot org
            Product|systemtap                   |netresolve
           Severity|normal                      |critical

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

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

[fche at redhat dot com]

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

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |fche at redhat dot com
          Component|core                        |testsuite
         Resolution|---                         |WONTFIX
           Assignee|unassigned at sourceware dot org   |systemtap at sourceware dot org
            Product|netresolve                  |systemtap

--- Comment #5 from Frank Ch. Eigler <fche at redhat dot com> ---
no recent interest

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

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

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2008-04-25 12:55 -------
> 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.

Ah, this is why you needed to use valgrind.
I don't think we can do exactly that from systemtap yet, since that would
require active interference with process memory mappings.  Maybe we need
a utrace extension & event source for just that -- "touched a page for
the first time".  Until then, we can probably intercept the kernel's
response to these occurrences: a page fault, or a dirty page writeout.

-- 


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.

[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:05 -------
Another use-case; I'd love to be able to chase bugs like this:

    http://bugzilla.kernel.org/show_bug.cgi?id=7372

with a real-world trace, a cut-down Linux kernel, and simulated hardware :-)

-- 


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.

[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.

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

[mark at klomp dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|frysk-bugzilla at sourceware|systemtap at sources dot
                   |dot org                     |redhat dot com
             Status|NEW                         |ASSIGNED
          Component|general                     |tapsets
            Product|frysk                       |systemtap


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.