From: Ming Zhang <blackmagic02881@gmail.com>
To: linux-btrace@vger.kernel.org
Subject: how to explain the current process?
Date: Sun, 25 Mar 2007 14:45:41 +0000 [thread overview]
Message-ID: <1174833941.3625.10.camel@localhost.localdomain> (raw)
Hi All
I am using blktrace to trace a untar operation on a 400GB (already 80%
used) ext3 disk.
since journal in ext3 is at the beginning of ext3, so small LBA are
journal operations, and large lba should be inode or file data.
8,0 0 1081156 60.171965751 4929 P R [kjournald]
8,0 0 1081157 60.171965991 4929 I W 26079 + 8 [kjournald]
8,0 0 1081158 60.171966726 4929 U R [kjournald] 1
8,0 0 1081159 60.171968511 4929 D W 26079 + 8 [kjournald]
8,0 0 1081160 60.172249031 0 C W 26079 + 8 [0]
journal request
8,0 0 1081161 60.172306613 4944 Q W 733338903 + 8 [tar]
8,0 0 1081162 60.172307471 4944 G W 733338903 + 8 [tar]
8,0 0 1081163 60.172308435 4944 P R [tar]
8,0 0 1081164 60.172308798 4944 I W 733338903 + 8 [tar]
8,0 0 1081165 60.172311794 4944 Q W 733338911 + 8 [tar]
8,0 0 1081166 60.172312274 4944 M W 733338911 + 8 [tar]
file or inode
8,0 0 1081167 60.172327693 4929 U R [kjournald] 1
why here a R(read) come up? and what is the meaning of this "1" here?
8,0 0 1081168 60.172329564 4929 D W 733338903 + 16
[kjournald]
8,0 0 1081169 60.172773400 0 C W 733338903 + 16 [0]
why it is kjounrald here to "D" this request? is this because tar
already "finish" the request by writing to page cache and then when do
device io, current process is happened to be kjournald? i read the code
and it grabs current pid, so it looks so. but i still need a
confirmation here from your guys.
Thanks!
Ming
next reply other threads:[~2007-03-25 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 14:45 Ming Zhang [this message]
2007-03-27 10:58 ` how to explain the current process? Jens Axboe
2007-03-27 13:44 ` Ming Zhang
2007-03-27 13:58 ` Jens Axboe
2007-03-27 14:11 ` Ming Zhang
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=1174833941.3625.10.camel@localhost.localdomain \
--to=blackmagic02881@gmail.com \
--cc=linux-btrace@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