From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Cc: trivial@rustcorp.com.au
Subject: [patch] remove space in /proc/slabinfo cache_name
Date: Sat, 25 May 2002 14:33:56 -0400 [thread overview]
Message-ID: <20020525143356.B323@rushmore> (raw)
Most /proc/slabinfo cache_names are in the format:
cache_name. There are a couple with spaces in the
name, which is inconsistent and requires a special case
when scripting.
Changes "fasync cache" and "file lock cache" to have
the usual underscore.
Tested on 2.5.18. Applies to 2.4.19-pre8 with offset.
diff -ruN linux-2.5.18/fs/fcntl.c linux-2.5.18.new/fs/fcntl.c
--- linux-2.5.18/fs/fcntl.c 2002-05-25 05:26:44.000000000 -0400
+++ linux-2.5.18.new/fs/fcntl.c 2002-05-25 06:12:52.000000000 -0400
@@ -551,7 +551,7 @@
static int __init fasync_init(void)
{
- fasync_cache = kmem_cache_create("fasync cache",
+ fasync_cache = kmem_cache_create("fasync_cache",
sizeof(struct fasync_struct), 0, 0, NULL, NULL);
if (!fasync_cache)
panic("cannot create fasync slab cache");
diff -ruN linux-2.5.18/fs/locks.c linux-2.5.18.new/fs/locks.c
--- linux-2.5.18/fs/locks.c 2002-05-21 01:07:37.000000000 -0400
+++ linux-2.5.18.new/fs/locks.c 2002-05-25 06:13:34.000000000 -0400
@@ -1940,7 +1940,7 @@
static int __init filelock_init(void)
{
- filelock_cache = kmem_cache_create("file lock cache",
+ filelock_cache = kmem_cache_create("file_lock_cache",
sizeof(struct file_lock), 0, 0, init_once, NULL);
if (!filelock_cache)
panic("cannot create file lock slab cache");
--
Randy Hron
next reply other threads:[~2002-05-25 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 18:33 rwhron [this message]
2002-05-25 19:07 ` [patch] remove space in /proc/slabinfo cache_name Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2002-05-25 19:23 rwhron
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=20020525143356.B323@rushmore \
--to=rwhron@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.