From: Jens Axboe <axboe@suse.de>
To: bert hubert <ahu@ds9a.nl>, linux-kernel@vger.kernel.org
Subject: Re: blockfile access patterns logging
Date: Thu, 8 Jan 2004 15:08:30 +0100 [thread overview]
Message-ID: <20040108140830.GR16720@suse.de> (raw)
In-Reply-To: <20040108120008.GA7415@outpost.ds9a.nl>
On Thu, Jan 08 2004, bert hubert wrote:
> 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).
>
> 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?
If you have the laptop mode patch (it's in 2.4 current, and in 2.6-mm as
well), then you can enable block dump by echoing 1 to
/proc/sys/vm/block_dump - this will dump all reads/writes to any device
in the system. Sounds like this is what you want.
--
Jens Axboe
next prev parent reply other threads:[~2004-01-08 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 12:00 blockfile access patterns logging bert hubert
2004-01-08 14:08 ` Jens Axboe [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 14:11 Samium Gromoff
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=20040108140830.GR16720@suse.de \
--to=axboe@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.