From: Pete Zaitcev <zaitcev@redhat.com>
To: aneesh.kumar@digital.com, linux-kernel@vger.kernel.org
Subject: Re: /proc/slabinfo doesn't give details of what it is showing.
Date: Mon, 1 Oct 2001 13:09:34 -0400 [thread overview]
Message-ID: <200110011709.f91H9Yq31791@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1001919360.11119.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.1001919360.11119.linux-kernel2news@redhat.com>
> len += sprintf(page+len, "slabinfo - version: 1.1"
> #if STATS
> " (statistics)"
> #endif
> #ifdef CONFIG_SMP
> " (SMP)"
> #endif
> "\n");
> len += sprintf(page+len,
> "(cache-name)-----(num-active-objs)--(total-objs)--(obj-size)--(num-active-slabs)--(total-slabs)--(num-pages-per-slab)\n");
0. This is an incompatible change that is going to break userland.
1. Learn to use diff -u.
2. Headers are customarily separated by spaces, not dashes.
-- Pete
next parent reply other threads:[~2001-10-01 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1001919360.11119.linux-kernel2news@redhat.com>
2001-10-01 17:09 ` Pete Zaitcev [this message]
2001-10-01 6:54 Aneesh Kumar K.V
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=200110011709.f91H9Yq31791@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=aneesh.kumar@digital.com \
--cc=linux-kernel@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
Powered by JetHome