From: Benjamin LaHaise <bcrl@redhat.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] improve wchan reporting
Date: Thu, 3 Oct 2002 18:48:54 -0400 [thread overview]
Message-ID: <20021003184854.I16875@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0210031928590.22735-100000@imladris.surriel.com>; from riel@conectiva.com.br on Thu, Oct 03, 2002 at 07:30:13PM -0300
On Thu, Oct 03, 2002 at 07:30:13PM -0300, Rik van Riel wrote:
> A third option could be a /proc/$pid/backtrace file which
> contains the whole backtrace for a process and teach procps
> to ignore certain functions.
It should really be a separate filesystem, though....
> I prefer your solution, though ;)
There's another problem with the way wchan is currently calculated: it's
relatively expensive to calculate. Many of the readers of stat don't actually
care about it. By making wchan a value in the task structure, the cost of
reading it is trivial.
-ben
--
GMS rules.
next prev parent reply other threads:[~2002-10-03 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 22:21 [patch] improve wchan reporting Benjamin LaHaise
2002-10-03 22:30 ` Rik van Riel
2002-10-03 22:48 ` Benjamin LaHaise [this message]
2002-10-04 14:10 ` Keith Owens
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=20021003184854.I16875@redhat.com \
--to=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.