From: Muli Ben-Yehuda <mulix@mulix.org>
To: Robert Love <rml@tech9.net>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Chris Rivera <cmrivera@ufl.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] slab information utility
Date: Mon, 22 Sep 2003 08:45:11 +0300 [thread overview]
Message-ID: <20030922054511.GH4938@actcom.co.il> (raw)
In-Reply-To: <1064208319.8888.248.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Mon, Sep 22, 2003 at 01:25:19AM -0400, Robert Love wrote:
> On Mon, 2003-09-22 at 01:17, William Lee Irwin III wrote:
>
> > I wrote something I called this earlier on; I'll withdraw any claim of
> > mine on the name since this utility is clearly superior to it and I'd
> > rather endorse it than my own creation.
>
> Sweet. Hope you like it. I think its very valuable during all sorts of
> kernel debugging (or even simple administrating), because everything is
> tied into the slab layer but /proc/slabinfo, while useful information,
> is impossible to grok.
I used to have a patch that implemented a /sysfs/slab/ layer, where
you could get all of the /proc/slabinfo information via sysfs
conveniently. Sadly, it went to wherever bad harddisks go when they
die. Since I need it for a different endeavour, I'll ressurect it
eventually. That should make the parsing in slabinfo a lot simpler.
Cheers,
Muli
--
Muli Ben-Yehuda
http://www.mulix.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-09-22 5:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 3:03 [ANNOUNCE] slab information utility Chris Rivera
2003-09-22 4:23 ` Herbert Poetzl
2003-09-22 4:39 ` Robert Love
2003-09-22 4:43 ` Herbert Poetzl
2003-09-22 5:17 ` Robert Love
2003-09-22 13:16 ` Herbert Poetzl
2003-09-22 5:18 ` Andrew Morton
2003-09-22 5:21 ` Robert Love
2003-09-22 5:17 ` William Lee Irwin III
2003-09-22 5:25 ` Robert Love
2003-09-22 5:45 ` Muli Ben-Yehuda [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=20030922054511.GH4938@actcom.co.il \
--to=mulix@mulix.org \
--cc=cmrivera@ufl.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=wli@holomorphy.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