From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: devel@driverdev.osuosl.org, Peng Tao <tao.peng@emc.com>,
Andreas Dilger <andreas.dilger@intel.com>,
linux-kernel@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH] staging: lustre: fix GFP_ATOMIC macro usage
Date: Fri, 17 Jan 2014 07:17:35 -0800 [thread overview]
Message-ID: <20140117151735.GB16623@kroah.com> (raw)
In-Reply-To: <20140117145128.GR7444@mwanda>
On Fri, Jan 17, 2014 at 05:51:28PM +0300, Dan Carpenter wrote:
> We will want to get rid of lustre's custom allocator before this gets
> out of staging.
>
> But one feature that the lustre allocator has which is pretty neat is
> that it lets you debug how much memory the filesystem is using. Is
> there a standard way to find this information?
Create your own mempool/slab/whatever_it's_called and look in the
debugfs or proc files for the allocator usage, depending on the memory
allocator the kernel is using.
That's how the rest of the kernel does it, no reason lustre should be
any different.
thanks,
greg k-h
next prev parent reply other threads:[~2014-01-17 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 8:46 [PATCH] staging: lustre: fix GFP_ATOMIC macro usage Marek Szyprowski
2014-01-17 14:33 ` Greg Kroah-Hartman
2014-01-17 14:51 ` Dan Carpenter
2014-01-17 15:17 ` Greg Kroah-Hartman [this message]
2014-01-21 20:02 ` Dilger, Andreas
2014-01-21 20:16 ` Dan Carpenter
2014-01-22 1:31 ` Drokin, Oleg
2014-01-21 21:15 ` Dave Hansen
2014-01-22 1:52 ` Drokin, Oleg
2014-01-20 8:18 ` Marek Szyprowski
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=20140117151735.GB16623@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=tao.peng@emc.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