From: fche@redhat.com (Frank Ch. Eigler)
To: Chris Snook <csnook@redhat.com>
Cc: Martin Knoblauch <knobi@knobisoft.de>,
linux-kernel@vger.kernel.org,
Peter zijlstra <a.p.zijlstra@chello.nl>,
Fengguang Wu <wfg@mail.ustc.edu.cn>,
systemtap@sources.redhat.com
Subject: Re: How to find out, what "pdflush" is working on
Date: Fri, 26 Sep 2008 21:26:00 -0000 [thread overview]
Message-ID: <y0mk5cymwh2.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <48D003F1.50101@redhat.com> (Chris Snook's message of "Tue, 16 Sep 2008 15:07:29 -0400")
> [...]
>> Is there a way to find out what a certain instance of "pdflush" is
>> working on? Like which block-device or which fliesystem it is
>> writing to? [...]
Something based upon the following systemtap script may help:
probe kernel.function("__writeback_single_inode") {
if (execname() == "pdflush")
printf("pdflush %d writeback bdev %x inode %x\n", tid(), $inode->i_rdev, $inode->i_ino)
}
Other fields are available as $inode->FOO.
- FChE
parent reply other threads:[~2008-09-26 21:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <48D003F1.50101@redhat.com>]
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=y0mk5cymwh2.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=csnook@redhat.com \
--cc=knobi@knobisoft.de \
--cc=linux-kernel@vger.kernel.org \
--cc=systemtap@sources.redhat.com \
--cc=wfg@mail.ustc.edu.cn \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).