From: Bart Samwel <bart@samwel.tk>
To: Kai Krueger <kai.a.krueger@web.de>, axboe@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Laptop-mode v7 for linux 2.6.1
Date: Tue, 13 Jan 2004 12:58:05 +0100 [thread overview]
Message-ID: <4003DD4D.1000305@samwel.tk> (raw)
In-Reply-To: <200401130110.i0D1ALQ08941@mailgate5.cinetic.de>
Kai Krueger wrote:
> I can not see any log entries for "kdeinit: [some pid]: dirtied page". There are only the "kdeinit: () WRITE block 65680 on hda1". By the way, it is always block 65680; also across reboots if that is any indication and I have seen other processes like artsd write to that block without dirtying pages before as well.
> Is there a way to find out what kdeinit writes to disk?
Ehm... I don't know how to go from a block to a filename on reiserfs.
Jens, do you have an idea?
Anyway, the other possibility is to use other file activity monitoring
tools. Some fam client maybe (couldn't find any so quickly); maybe
Filemon (http://www.sysinternals.com/linux/utilities/filemon.shtml) will
work, but I don't know if it works for Linux 2.6. You may also try "lsof
| grep kded", and see if it's one of those files. For me, it gives:
# lsof |grep kded
kdeinit 1185 bsamwel mem REG 3,65 117196 5146489
/usr/lib/kded.so
kdeinit 1185 bsamwel mem REG 3,65 111412 9470211
/usr/lib/kde3/kded_mountwatcher.so
kdeinit 1185 bsamwel mem REG 3,65 62408 9470683
/usr/lib/kde3/kded_kinetd.so
Alternatively, you can try to attach an strace for kdeinit: kded, and
see what calls it makes, e.g. "strace -p <pid>" or something like that.
-- Bart
next prev parent reply other threads:[~2004-01-13 11:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 1:10 [PATCH] Laptop-mode v7 for linux 2.6.1 Kai Krueger
2004-01-13 11:58 ` Bart Samwel [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 17:07 Kai Krueger
2004-01-12 19:31 ` Bart Samwel
2004-01-12 20:51 ` Dumitru Ciobarcianu
2004-01-12 21:50 ` Bart Samwel
2004-01-12 22:51 ` Andrew Morton
2004-01-10 10:38 Bart Samwel
2004-01-10 11:15 ` Dax Kelson
2004-01-12 9:45 ` Jan De Luyck
2004-01-12 9:59 ` Bart Samwel
2004-01-12 12:50 ` Dax Kelson
2004-01-12 12:59 ` Bart Samwel
2004-01-12 15:04 ` Valdis.Kletnieks
2004-01-12 11:12 ` Jan De Luyck
2004-01-12 11:22 ` Bart Samwel
2004-01-12 12:43 ` Jan De Luyck
2004-01-12 13:41 ` Bart Samwel
2004-01-12 13:32 ` Hugang
2004-01-12 17:30 ` Dumitru Ciobarcianu
2004-01-12 12:19 ` Kiko Piris
2004-01-12 12:45 ` Jan De Luyck
2004-01-12 13:09 ` Jan De Luyck
2004-01-12 14:02 ` Jens Axboe
2004-01-13 11:00 ` Jan De Luyck
2004-01-13 11:01 ` Jens Axboe
2004-01-13 12:46 ` Bart Samwel
2004-01-13 14:21 ` Hugang
2004-01-13 17:17 ` Jan De Luyck
2004-02-11 6:24 ` Jan De Luyck
2004-02-11 13:00 ` Micha Feigin
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=4003DD4D.1000305@samwel.tk \
--to=bart@samwel.tk \
--cc=axboe@suse.de \
--cc=kai.a.krueger@web.de \
--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.