From: Ryan Mack <rmack@mackman.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] slab cache name changes (trivial)
Date: Wed, 17 Apr 2002 12:12:30 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0204171208130.14881-200000@mackman.net> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 324 bytes --]
A few of the slab caches had names containing spaces which breaks a few
slabinfo parsing scripts I use. It seems the consensus is to use
underscores instead of spaces in slab cache names, and this patch corrects
those names still using spaces. Applies cleanly against 2.4.18 and with
offsets on 2.4.19-pre7.
Thanks, Ryan
[-- Attachment #2: Type: TEXT/PLAIN, Size: 1342 bytes --]
diff -aur linux-orig/fs/dnotify.c linux/fs/dnotify.c
--- linux-orig/fs/dnotify.c Tue Nov 7 23:27:57 2000
+++ linux/fs/dnotify.c Wed Apr 17 12:02:46 2002
@@ -131,7 +131,7 @@
static int __init dnotify_init(void)
{
- dn_cache = kmem_cache_create("dnotify cache",
+ dn_cache = kmem_cache_create("dnotify_cache",
sizeof(struct dnotify_struct), 0, 0, NULL, NULL);
if (!dn_cache)
panic("cannot create dnotify slab cache");
diff -aur linux-orig/fs/fcntl.c linux/fs/fcntl.c
--- linux-orig/fs/fcntl.c Mon Sep 17 13:16:30 2001
+++ linux/fs/fcntl.c Wed Apr 17 12:03:29 2002
@@ -525,7 +525,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 -aur linux-orig/fs/locks.c linux/fs/locks.c
--- linux-orig/fs/locks.c Thu Oct 11 07:52:18 2001
+++ linux/fs/locks.c Wed Apr 17 12:03:22 2002
@@ -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");
reply other threads:[~2002-04-17 19:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.44.0204171208130.14881-200000@mackman.net \
--to=rmack@mackman.net \
--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;
as well as URLs for NNTP newsgroup(s).