Disk tap

Simon Kirby (sim@netnation.com)
Sun, 31 May 1998 11:28:58 -0700 (PDT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Andi Kleen: "Re: overloading system calls."
Previous message: Andrea Arcangeli: "Re: test_and_set_bit() not atomic forever? [cli/sti in char/vt.c [patch]]"

Has anybody invented any sort of "Disk tap" device that, upon reading,
shows you what is being read and written from/to each block device on the
system? If not, is anybody else interested in something like this? I
know there have been a few times when I want to find out what program is
churning the disk, and it's pretty hard to figure out sometimes.

I was thinking something up to the level where you could see what inodes
were being accessed...and maybe even have it look up the filenames, but
that would be more complicated. It'd probably be inside the ext2 layer
(before dcache), not similar to hooking the raw read/write functions.

Simon-

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

Next message: Andi Kleen: "Re: overloading system calls."
Previous message: Andrea Arcangeli: "Re: test_and_set_bit() not atomic forever? [cli/sti in char/vt.c [patch]]"