public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samium Gromoff <deepfire@sic-elvis.zel.ru>
To: ahu@ds9a.nl
Cc: linux-kernel@vger.kernel.org
Subject: blockfile access patterns logging
Date: Thu, 08 Jan 2004 17:11:19 +0300	[thread overview]
Message-ID: <87ad4y8r94.wl@canopus.ns.zel.ru> (raw)


> Jens,                                                                                    
>                                                                                          
> For some time I've wanted to log exactly what linux is reading and writing               
> from my harddisk - for a variety of reasons. The current reason is that my               
> very idle laptop writes to disk every once in a while (or reads, I don't                 
> know).                                                                                   

Have you mounted the fs with -o noatime?

> Now, conceptually this should not be very hard, but I'd like to ask your                 
> thoughts on where I might insert some crude logging? There are lots of                   
> places that might be better or worse for some reason.                                    
>                                                                                          
> I'd love to be as close to the physical block device as possible, short of               
> rewriting actual IDE drivers.                                                            
>                                                                                          
> Any tips? Or is this idea crazy?                                                         
>                                                                                          
> Thanks!                                                                                  
>                                                                                          
> --                                                                                       
> http://www.PowerDNS.com      Open source, database driven DNS Software                   
> http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO                

regards, Samium Gromoff



             reply	other threads:[~2004-01-08 14:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 14:11 Samium Gromoff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-08 12:00 blockfile access patterns logging bert hubert
2004-01-08 14:08 ` Jens Axboe
2004-01-08 14:30 ` Valdis.Kletnieks
2004-01-08 14:39   ` Jens Axboe
2004-01-08 14:54     ` Valdis.Kletnieks
2004-01-08 14:58       ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ad4y8r94.wl@canopus.ns.zel.ru \
    --to=deepfire@sic-elvis.zel.ru \
    --cc=ahu@ds9a.nl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox