linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: penberg@cs.helsinki.fi, cl@linux-foundation.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/4] kmemtrace: Core implementation.
Date: Fri, 18 Jul 2008 02:49:01 +0300	[thread overview]
Message-ID: <20080717234901.GA5233@localhost> (raw)
In-Reply-To: <20080717143434.79b33fe9.rdunlap@xenotime.net>

On Thu, Jul 17, 2008 at 02:34:34PM -0700, Randy Dunlap wrote:
> On Thu, 17 Jul 2008 03:46:45 +0300 Eduard - Gabriel Munteanu wrote:
> 
> > +3) Boot the kmemtrace-enabled kernel if you haven't, preferably in the
> > +'single' runlevel (so that relay buffers don't fill up easily), and run
> > +kmemtrace:
> > +# '$' does not mean user, but root here.
> > +$ mount -t debugfs none /debug
> 
> Please mount at /sys/kernel/debug, i.e., the expected debugfs mount point.
> 

Oh, I did not know that. Thanks, will change accordingly.

> > +$ mount -t proc none /proc
> > +$ cd path/to/kmemtrace-user/
> > +$ ./kmemtraced
> > +Wait a bit, then stop it with CTRL+C.
> > +$ cat /debug/kmemtrace/total_overruns	# Check if we didn't overrun, should
> > +					# be zero.
> > +$ (Optionally) [Run kmemtrace_check separately on each cpu[0-9]*.out file to
> > +		check its correctness]
> > +$ ./kmemtrace-report
> > +
> > +Now you should have a nice and short summary of how the allocator performs.
> 
> 
> Otherwise looks nice.  Thanks.
> 
> ---
> ~Randy
> Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
> http://linuxplumbersconf.org/

--
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:[~2008-07-17 23:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17  0:46 [RFC PATCH 0/4] kmemtrace RFC (resubmit 1) Eduard - Gabriel Munteanu
2008-07-17  0:46 ` [RFC PATCH 1/4] kmemtrace: Core implementation Eduard - Gabriel Munteanu
2008-07-17  0:46   ` [RFC PATCH 2/4] kmemtrace: SLAB hooks Eduard - Gabriel Munteanu
2008-07-17  0:46     ` [RFC PATCH 3/4] kmemtrace: SLUB hooks Eduard - Gabriel Munteanu
2008-07-17  0:46       ` [RFC PATCH 4/4] kmemtrace: SLOB hooks Eduard - Gabriel Munteanu
2008-07-17  7:43         ` Pekka Enberg
2008-07-17 15:46           ` Matt Mackall
2008-07-17  7:46       ` [RFC PATCH 3/4] kmemtrace: SLUB hooks Pekka Enberg
2008-07-17 18:06         ` Eduard - Gabriel Munteanu
2008-07-17  7:38     ` [RFC PATCH 2/4] kmemtrace: SLAB hooks Pekka Enberg
2008-07-17  8:01   ` [RFC PATCH 1/4] kmemtrace: Core implementation Pekka Enberg
2008-07-17 18:32     ` Eduard - Gabriel Munteanu
2008-07-18  8:48       ` Pekka J Enberg
2008-07-18 10:13         ` Eduard - Gabriel Munteanu
2008-07-18 14:38           ` Pekka Enberg
2008-07-18 19:40             ` Eduard - Gabriel Munteanu
2008-07-18 20:07               ` Matt Mackall
2008-07-17 21:34   ` Randy Dunlap
2008-07-17 23:49     ` Eduard - Gabriel Munteanu [this message]
2008-07-22 18:31 [RFC PATCH 0/4] kmemtrace RFC (resend 2) Eduard - Gabriel Munteanu
2008-07-22 18:31 ` [RFC PATCH 1/4] kmemtrace: Core implementation Eduard - Gabriel Munteanu
2008-07-22 21:28   ` Frank Ch. Eigler
2008-07-23  0:50     ` Eduard - Gabriel Munteanu
2008-07-23  0:55       ` Eduard - Gabriel Munteanu
2008-07-23  1:26       ` Frank Ch. Eigler
2008-07-22 18:36 [RFC PATCH 0/4] kmemtrace RFC (resend 2, fixed wrong Cc) Eduard - Gabriel Munteanu
2008-07-22 18:36 ` [RFC PATCH 1/4] kmemtrace: Core implementation Eduard - Gabriel Munteanu
2008-07-28  9:24   ` Pekka Enberg
2008-07-28 16:29     ` Mathieu Desnoyers
2008-07-28 17:09       ` Matt Mackall
2008-07-28 17:35       ` Eduard - Gabriel Munteanu
2008-07-29  8:25         ` Pekka Enberg

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=20080717234901.GA5233@localhost \
    --to=eduard.munteanu@linux360.ro \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=rdunlap@xenotime.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox