From: Ben Greear <greearb@candelatech.com>
To: Christoph Lameter <cl@linux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] slub: Enable backtrace for create/delete points.
Date: Wed, 06 Oct 2010 13:53:04 -0700 [thread overview]
Message-ID: <4CACE1B0.5000409@candelatech.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010061527560.6878@router.home>
On 10/06/2010 01:32 PM, Christoph Lameter wrote:
> On Wed, 6 Oct 2010, greearb@candelatech.com wrote:
>
>> This patch attempts to grab a backtrace for the creation
>> and deletion points of the slub object. When a fault is
>> detected, we can then get a better idea of where the item
>> was deleted.
>
> We have had patches like that for SLAB in the past. The backtrace was
> typically limited to 4 entries I believe.
Even 8 didn't show enough to be useful in my case, so I bumped it to 16,
but it would be easier to edit a #define than re-hack the entire
patch each time someone wanted such a thing...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2010-10-06 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 20:08 [RFC] slub: Enable backtrace for create/delete points greearb
2010-10-06 20:32 ` Christoph Lameter
2010-10-06 20:53 ` Ben Greear [this message]
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=4CACE1B0.5000409@candelatech.com \
--to=greearb@candelatech.com \
--cc=cl@linux.com \
--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 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.