All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-btrfs@vger.kernel.org, zab@zabbo.net, cl@linux.com,
	penberg@kernel.org
Subject: Re: [PATCH V2] mm/slab: add a leak decoder callback
Date: Fri, 18 Jan 2013 09:12:59 +0800	[thread overview]
Message-ID: <20130118011258.GE6768@liubo> (raw)
In-Reply-To: <50F63BEE.8040506@cn.fujitsu.com>

On Wed, Jan 16, 2013 at 01:34:38PM +0800, Miao Xie wrote:
> On wed, 16 Jan 2013 11:03:13 +0800, Liu Bo wrote:
> > This adds a leak decoder callback so that slab destruction
> > can use to generate debugging output for the allocated objects.
> > 
> > Callers like btrfs are using their own leak tracking which will
> > manage allocated objects in a list(or something else), this does
> > indeed the same thing as what slab does.  So adding a callback
> > for leak tracking can avoid this as well as runtime overhead.
> 
> If the slab is merged with the other one, this patch can work well?

Yes and no, so I'll disable merging slab in the next version :)

thanks,
liubo

WARNING: multiple messages have this Message-ID (diff)
From: Liu Bo <bo.li.liu@oracle.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-btrfs@vger.kernel.org, zab@zabbo.net, cl@linux.com,
	penberg@kernel.org
Subject: Re: [PATCH V2] mm/slab: add a leak decoder callback
Date: Fri, 18 Jan 2013 09:12:59 +0800	[thread overview]
Message-ID: <20130118011258.GE6768@liubo> (raw)
In-Reply-To: <50F63BEE.8040506@cn.fujitsu.com>

On Wed, Jan 16, 2013 at 01:34:38PM +0800, Miao Xie wrote:
> On wed, 16 Jan 2013 11:03:13 +0800, Liu Bo wrote:
> > This adds a leak decoder callback so that slab destruction
> > can use to generate debugging output for the allocated objects.
> > 
> > Callers like btrfs are using their own leak tracking which will
> > manage allocated objects in a list(or something else), this does
> > indeed the same thing as what slab does.  So adding a callback
> > for leak tracking can avoid this as well as runtime overhead.
> 
> If the slab is merged with the other one, this patch can work well?

Yes and no, so I'll disable merging slab in the next version :)

thanks,
liubo

--
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>

  reply	other threads:[~2013-01-18  1:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16  3:03 [PATCH V2] mm/slab: add a leak decoder callback Liu Bo
2013-01-16  3:03 ` Liu Bo
2013-01-16  5:34 ` Miao Xie
2013-01-16  5:34   ` Miao Xie
2013-01-18  1:12   ` Liu Bo [this message]
2013-01-18  1:12     ` Liu Bo
2013-01-16 15:20 ` Christoph Lameter
2013-01-16 15:20   ` Christoph Lameter
2013-01-18  1:11   ` Liu Bo
2013-01-18  1:11     ` Liu Bo
2013-01-17  8:34 ` Joonsoo Kim
2013-01-17  8:34   ` Joonsoo Kim
2013-01-18  0:59   ` Liu Bo
2013-01-18  0:59     ` Liu Bo

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=20130118011258.GE6768@liubo \
    --to=bo.li.liu@oracle.com \
    --cc=cl@linux.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=miaox@cn.fujitsu.com \
    --cc=penberg@kernel.org \
    --cc=zab@zabbo.net \
    /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.