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" ;) > I don't think you understand what Bert is looking for. He explicitly > mentions that the machine is very idle, so he's probably looking for > culprits that spin up the drive occasionally. Oh, I understand very well.. Been there myself. I'd just forgotten that the laptop patch provided the process-ID information. ;)
Attachment:
pgp354917.pgp
Description: PGP signature
Follow-Ups:
- Re: blockfile access patterns loggingJens Axboe
- blockfile access patterns loggingbert hubert
- Re: blockfile access patterns loggingValdis.Kletnieks
- Re: blockfile access patterns loggingJens Axboe
- Prev by Date: RFC: ACPI table overflow handling
- Next by Date: 2.6.0-rc2-mm1: function called from invalid context at mm/page_alloc.c:550
- Previous by thread: Re: blockfile access patterns logging
- Next by thread: Re: blockfile access patterns logging
- Indexes:[Main][Thread]