I/O tracing

• Next message: Jeff Garzik: "Re: [PATCH] support for Cobalt Networks (x86 only) systems (forrealthis"
• Previous message: Kevin P. Fleming: "2.4.5(-ac*] still broken NFS/Reiserfs"
• Next in thread: richardj_moore@uk.ibm.com: "Re: I/O tracing"
• Maybe reply: richardj_moore@uk.ibm.com: "Re: I/O tracing"
• Reply: Mike Galbraith: "Re: I/O tracing"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,
        Please CC me as I'm not subscribed on the list, thanks. Not sure if
this is appropriate forum, is there an existing tool/module for capturing
all the I/O requests such as:

Unique Identifier
Start Time
End Time
Device Identifier
Operation Type (Read Or Write)
Offset
Length (Number Of Bytes)

I am aware of existing /proc/disks and partitions, but these aren't real
time. If not, are there any facilities in the kernel I can put a hook in to
keep track of the I/O?

Thanks in advance,
Sammy Yu
Hewlett-Packard

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Jeff Garzik: "Re: [PATCH] support for Cobalt Networks (x86 only) systems (forrealthis"
• Previous message: Kevin P. Fleming: "2.4.5(-ac*] still broken NFS/Reiserfs"
• Next in thread: richardj_moore@uk.ibm.com: "Re: I/O tracing"
• Maybe reply: richardj_moore@uk.ibm.com: "Re: I/O tracing"
• Reply: Mike Galbraith: "Re: I/O tracing"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Jun 07 2001 - 21:00:30 EST