kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: gmate.amit@gmail.com (Kumar Amit Mehta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Memory profiling tools for Linux Kernel
Date: Fri, 4 Apr 2014 15:06:53 +0300	[thread overview]
Message-ID: <20140404120653.GB12452@gmail.com> (raw)
In-Reply-To: <CAOMGZ=H7HS-KPbVq3=cagrvJ3Ya_g8swmbv5hMf4QzygSW9XMg@mail.gmail.com>

On Fri, Apr 04, 2014 at 10:34:54AM +0200, Vegard Nossum wrote:
> On 4 April 2014 02:45, Kumar Amit Mehta <gmate.amit@gmail.com> wrote:
> > I was looking for some tools for memory profiling for Linux Kernel. I
> > I wish to analyze the memory usage statistics by comparing the results
> > (with and without the usage of Lookaside caches) by the consumer (Say
> > a certain driver).I found some tools such as kmemcheck[1] and KEDR [2]
> > but before I go further and explore these tools, I was wondering if
> > somebody has already used these tools to acquire similar statistics
> > or I should try out some other tool.
> >
> > [1] https://www.kernel.org/doc/Documentation/kmemcheck.txt
> > [2] http://kedr.berlios.de/
> 
> Hi,
> 
> kmemcheck will probably not help you with memory usage statistics. It
> may help you find certain programming errors (use after free, use of
> uninitialised memory, etc.).
> 
> The slab allocator exports some information about memory allocations
> that may or may not give you what you need. Try e.g. 'sudo slabtop'.

Thank you for the information, I'll try that out. My main objective is
to find out the performance gain a consumer might achieve by using
lookaside caches, memory pool etc than by doing normal memory allocation
primitives(kmalloc/vmalloc).

Thanks,
Kumar

      parent reply	other threads:[~2014-04-04 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04  0:45 Memory profiling tools for Linux Kernel Kumar Amit Mehta
2014-04-04  8:34 ` Vegard Nossum
2014-04-04  8:49   ` aaditya.gavandalkar at yahoo.com
2014-04-04 12:09     ` Kumar Amit Mehta
2014-04-04 11:56   ` Pietro Paolini
2014-04-04 12:06   ` Kumar Amit Mehta [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=20140404120653.GB12452@gmail.com \
    --to=gmate.amit@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).