From: Mark Seger <Mark.Seger@hp.com>
To: util-linux-ng@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, Christoph Lameter <clameter@sgi.com>
Subject: Supports for new slab allocator now in latest release
Date: Sat, 05 Jan 2008 14:29:44 -0500 [thread overview]
Message-ID: <477FDAA8.2030001@hp.com> (raw)
I just wanted to let people know that as a result of a discussion on
linux-mm I've added support for the new slab allocator to my collectl
utility, now making it real easy to dynamically monitor allocations
along with all the other types of monitoring collectl does. I've also
put together a webpage at http://collectl.sourceforge.net/SlabInfo.html
to give a taste of how this all works as well as to show a few different
types of output.
-mark
--
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>
next reply other threads:[~2008-01-05 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 19:29 Mark Seger [this message]
2009-03-12 13:14 ` New release of collectl now supports NFS V4 and buddyinfo Seger, Mark
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=477FDAA8.2030001@hp.com \
--to=mark.seger@hp.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=util-linux-ng@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox