Re: blockfile access patterns logging

[Jens Axboe <axboe _at_ xxxxxxx>]

On Thu, Jan 08 2004, Valdis.Kletnieks _at_ vt.edu wrote:
> On Thu, 08 Jan 2004 15:39:08 +0100, Jens Axboe said:
> 
> > For laptops, it's often most interesting to find out _what_ process
> > dirtied what data (which in turn caused bdflush to sync it), or what
> > process keeps doing small reads. And block_dump does exactly that (it
> > was invented for exactly that purpose :)
> 
> I submit that "what process ID did it" is even more remote from the disk
> than "what inode" ;)

There are no inodes involved at that point, it's left the fs and is
purely in area between block layer and disk driver. Besides, what would
do with the inode for this problem? If you really want to find eg the
file in question (if you cannot _guess_ when you know the process), then
you could go back from the block number. I've never ever had a need to
go that far, though.

-- 
Jens Axboe

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