From: "Jörn Engel" <joern@logfs.org>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: Christoph Lameter <cl@linux-foundation.org>,
penberg <penberg@cs.helsinki.fi>, mpm <mpm@selenic.com>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] slub: reduce total stack usage of slab_err & object_err
Date: Tue, 30 Sep 2008 21:33:19 +0200 [thread overview]
Message-ID: <20080930193318.GA31146@logfs.org> (raw)
In-Reply-To: <1222787736.2995.24.camel@castor.localdomain>
On Tue, 30 September 2008 16:15:36 +0100, Richard Kennedy wrote:
>
> I've been trying to build a tool to estimate the maximum stack usage in
> the kernel, & noticed that most of the biggest stack users are the error
> handling routines.
Cool! I once did the same, although the code has severely bitrotted by
now. Is the code available somewhere?
Jörn
--
"Error protection by error detection and correction."
-- from a university class
WARNING: multiple messages have this Message-ID (diff)
From: "Jörn Engel" <joern@logfs.org>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: Christoph Lameter <cl@linux-foundation.org>,
penberg <penberg@cs.helsinki.fi>, mpm <mpm@selenic.com>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] slub: reduce total stack usage of slab_err & object_err
Date: Tue, 30 Sep 2008 21:33:19 +0200 [thread overview]
Message-ID: <20080930193318.GA31146@logfs.org> (raw)
In-Reply-To: <1222787736.2995.24.camel@castor.localdomain>
On Tue, 30 September 2008 16:15:36 +0100, Richard Kennedy wrote:
>
> I've been trying to build a tool to estimate the maximum stack usage in
> the kernel, & noticed that most of the biggest stack users are the error
> handling routines.
Cool! I once did the same, although the code has severely bitrotted by
now. Is the code available somewhere?
JA?rn
--
"Error protection by error detection and correction."
-- from a university class
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-09-30 19:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 15:15 [PATCH] slub: reduce total stack usage of slab_err & object_err Richard Kennedy
2008-09-30 15:15 ` Richard Kennedy
2008-09-30 15:32 ` Matt Mackall
2008-09-30 15:32 ` Matt Mackall
2008-09-30 15:38 ` Christoph Lameter
2008-09-30 15:38 ` Christoph Lameter
2008-09-30 15:49 ` Matt Mackall
2008-09-30 15:49 ` Matt Mackall
2008-09-30 16:20 ` Richard Kennedy
2008-09-30 16:20 ` Richard Kennedy
2008-09-30 16:43 ` Matt Mackall
2008-09-30 16:43 ` Matt Mackall
2008-09-30 17:36 ` Christoph Lameter
2008-09-30 17:36 ` Christoph Lameter
2008-09-30 17:37 ` Matt Mackall
2008-09-30 17:37 ` Matt Mackall
2008-09-30 18:33 ` Matt Mackall
2008-09-30 18:33 ` Matt Mackall
2008-10-01 9:50 ` Richard Kennedy
2008-10-01 9:50 ` Richard Kennedy
2008-10-01 0:02 ` Matt Mackall
2008-10-01 0:02 ` Matt Mackall
2008-09-30 19:33 ` Jörn Engel [this message]
2008-09-30 19:33 ` Jörn Engel
2008-10-01 10:06 ` Richard Kennedy
2008-10-01 10:06 ` Richard Kennedy
2008-10-01 10:32 ` Jörn Engel
2008-10-01 10:32 ` Jörn Engel
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=20080930193318.GA31146@logfs.org \
--to=joern@logfs.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
--cc=richard@rsk.demon.co.uk \
/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.