From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Fengguang Wu <wfg@mail.ustc.edu.cn>,
hirofumi@mail.parknet.co.jp, galak@kernel.crashing.org,
zaitcev@redhat.com, greg@kroah.com,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, mbligh@google.com
Subject: Re: [PATCH] writeback: remove unnecessary wait in throttle_vm_writeout()
Date: Sat, 29 Sep 2007 06:25:22 +1000 [thread overview]
Message-ID: <200709290625.23043.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20070928175756.GA16066@Krystal>
On Saturday 29 September 2007 03:57, Mathieu Desnoyers wrote:
> Isn't the actual instrumentation present in the VM subsystem consisting
> mostly of event counters ? This kind of profiling provides limited help in
> following specific delays in the kernel. Martin Bligh's paper "Linux
> Kernel Debugging on Google-sized clusters", presented at OLS2007,
> discusses instrumentation that had to be added to the VM subsystem in
> order to find a race condition in the OOM killer by gathering a trace of
> the problematic behavior. Gathering a full trace (timestamps and events)
> seems to be better suited to this kind of timing-related problem.
AFAIK, nobody is nacking patches that add more generally useful
instrumentation to the vm.
You'll obviously always get problems that you need specialised
information to solve. Those kinds of corner cases are probably a
good idea for dynamic instrumentation I guess.
next prev parent reply other threads:[~2007-09-29 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070927015016.GA11080@mail.ustc.edu.cn>
2007-09-27 1:50 ` Fengguang Wu
2007-09-27 15:16 ` Rik van Riel
[not found] ` <20070928011846.GA5496@mail.ustc.edu.cn>
2007-09-28 1:18 ` Fengguang Wu
2007-09-27 20:47 ` Andrew Morton
2007-09-28 8:02 ` Ingo Molnar
2007-09-27 22:59 ` Nick Piggin
2007-09-28 16:23 ` Mathieu Desnoyers
2007-09-28 0:10 ` Nick Piggin
2007-09-28 17:57 ` Mathieu Desnoyers
2007-09-28 19:50 ` Frank Ch. Eigler
2007-09-28 20:25 ` Nick Piggin [this message]
2007-09-27 21:49 ` Nick Piggin
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=200709290625.23043.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=galak@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=wfg@mail.ustc.edu.cn \
--cc=zaitcev@redhat.com \
/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
Powered by JetHome