From: Chris Wright <chrisw@osdl.org>
To: davem@davemloft.net
Cc: netdev@oss.sgi.com
Subject: [PATCH 7/8] Use SLAB_PANIC when creating critical slab cache
Date: Sun, 14 Nov 2004 12:24:49 -0800 [thread overview]
Message-ID: <20041114122449.E2357@build.pdx.osdl.net> (raw)
In-Reply-To: <20041114121837.X2357@build.pdx.osdl.net>; from chrisw@osdl.org on Sun, Nov 14, 2004 at 12:18:37PM -0800
Use SLAB_PANIC when creating a critical slab cache.
Signed-off-by: Chris Wright <chrisw@osdl.org>
===== net/ipv6/route.c 1.101 vs edited =====
--- 1.101/net/ipv6/route.c 2004-11-11 15:07:25 -08:00
+++ edited/net/ipv6/route.c 2004-11-14 11:56:41 -08:00
@@ -2069,12 +2069,9 @@ void __init ip6_route_init(void)
struct proc_dir_entry *p;
ip6_dst_ops.kmem_cachep = kmem_cache_create("ip6_dst_cache",
- sizeof(struct rt6_info),
- 0, SLAB_HWCACHE_ALIGN,
- NULL, NULL);
- if (!ip6_dst_ops.kmem_cachep)
- panic("cannot create ip6_dst_cache");
-
+ sizeof(struct rt6_info), 0,
+ SLAB_HWCACHE_ALIGN|SLAB_PANIC,
+ NULL, NULL);
fib6_init();
#ifdef CONFIG_PROC_FS
p = proc_net_create("ipv6_route", 0, rt6_proc_info);
next prev parent reply other threads:[~2004-11-14 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 20:18 [PATCH 0/8] Use SLAB_PANIC when creating critical slab cache Chris Wright
2004-11-14 20:20 ` [PATCH 1/8] " Chris Wright
2004-11-14 20:20 ` [PATCH 2/8] " Chris Wright
2004-11-14 20:21 ` [PATCH 3/8] " Chris Wright
2004-11-14 20:22 ` [PATCH 4/8] " Chris Wright
2004-11-14 20:23 ` [PATCH 5/8] " Chris Wright
2004-11-14 20:24 ` [PATCH 6/8] " Chris Wright
2004-11-14 20:27 ` Arnaldo Carvalho de Melo
2004-11-14 22:51 ` Chris Wright
2004-11-14 23:51 ` Arnaldo Carvalho de Melo
2004-11-14 20:24 ` Chris Wright [this message]
2004-11-14 20:25 ` [PATCH 8/8] " Chris Wright
2004-11-14 23:11 ` [PATCH 0/8] " Christoph Hellwig
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=20041114122449.E2357@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).