From: Mark Hedges <hedges@ucsd.edu>
To: dean gaudet <dean@arctic.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unknown io writes in 2.6.16
Date: Mon, 15 May 2006 17:12:38 -0700 (PDT) [thread overview]
Message-ID: <20060515170943.P3338@network.ucsd.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.0605121012230.7292@twinlark.arctic.org>
On Fri, 12 May 2006, dean gaudet wrote:
> On Wed, 10 May 2006, Mark Hedges wrote:
>
> > Just a wishlist that process IO could be monitored. I hate to
> > say it but ctl-alt-esc in W2K can monitor io by process, and
> > that's really useful. (I will never go back though.)
>
> /etc/init.d/klogd stop
> echo 1 >/proc/sys/vm/block_dump
> /sbin/klogd -n -f -
>
> watch lots of spew
>
> ^C
> echo 0 >/proc/sys/vm/block_dump
> /etc/init.d/klogd start
>
> that will tell you a lot of stuff. it will probably lead you to a process
> or two as culprits... use strace(8) to attach to those and get more
> specific information.
>
> now... share with me how to do this on windoze? :) i'm trying to get rid
> of the last write or two on my laptop...
Cool, thanks, I'll check this out. It's actually about 12k
every 5 seconds, not 12 bytes. Seems excessive for atime
updates.
In W2K at any rate, ctl-shift-esc to get the task manager.
Processes tab. View Menu > Select Columns. Sort by column.
Mark
next prev parent reply other threads:[~2006-05-16 0:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 20:59 unknown io writes in 2.6.16 Mark Hedges
2006-05-10 21:42 ` David Rees
2006-05-11 5:54 ` Mark Hedges
2006-05-11 12:46 ` Giacomo A. Catenazzi
2006-05-11 13:23 ` Avi Kivity
2006-05-11 15:22 ` Erik Mouw
2006-05-12 17:17 ` dean gaudet
2006-05-16 0:12 ` Mark Hedges [this message]
2006-05-16 0:48 ` dean gaudet
2006-05-16 1:21 ` Con Kolivas
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=20060515170943.P3338@network.ucsd.edu \
--to=hedges@ucsd.edu \
--cc=dean@arctic.org \
--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