From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Need help tracing regular write activity in 5 s interval
Date: Sun, 2 Jun 2002 22:19:44 +0200 [thread overview]
Message-ID: <20020602201944.GA13682@merlin.emma.line.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0206020922410.29405-100000@hawkeye.luckynet.adm>
On Sun, 02 Jun 2002, Thunder from the hill wrote:
> Hi,
>
> > So: is there any trace software that can tell me "at 15:52:43.012345,
> > process 4321 marked 7 blocks dirty on device /dev/hda5" (or even more
> > detail so I can figure if it's just an atime update -- as with svscan --
> > or a write access)? And that is NOT to be attached to a specific process
> > (hint: strace is not an option).
>
> Problem: we'd have to do that using printk. printk issues another write
> call, which will mark things dirty. Issued is another printk, which marks
> things dirty and issues another printk...
Need not be printk, I can also imagine allocating a buffer, switching
this trace on, exempting the tracer from bein traced, and switching the
trace off if the buffer is full.
next prev parent reply other threads:[~2002-06-02 20:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 15:25 Thunder from the hill
2002-06-02 15:41 ` Kevin Krieser
2002-06-02 16:12 ` Kenneth Johansson
2002-06-02 20:19 ` Matthias Andree [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-02 13:55 Matthias Andree
2002-06-04 11:21 ` Padraig Brady
2002-06-04 11:41 ` Muli Ben-Yehuda
2002-06-04 11:43 ` Xavier Bestel
2002-06-04 12:04 ` Erik Andersen
2002-06-05 14:08 ` Padraig Brady
2002-06-05 15:13 ` Padraig Brady
2002-06-05 15:50 ` Owen Taylor
2002-06-05 16:43 ` Padraig Brady
2002-06-05 22:22 ` Padraig Brady
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=20020602201944.GA13682@merlin.emma.line.org \
--to=matthias.andree@stud.uni-dortmund.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®