netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Chris Wright <chrisw@osdl.org>
Cc: davem@davemloft.net, netdev@oss.sgi.com
Subject: Re: [PATCH 0/8] Use SLAB_PANIC when creating critical slab cache
Date: Sun, 14 Nov 2004 23:11:01 +0000	[thread overview]
Message-ID: <20041114231101.GA9498@infradead.org> (raw)
In-Reply-To: <20041114121837.X2357@build.pdx.osdl.net>

On Sun, Nov 14, 2004 at 12:18:37PM -0800, Chris Wright wrote:
> The following trivial patches update networking code to use the SLAB_PANIC
> flag when creating a critical slab cache instead of doing localized calls
> to panic().  This brings networking inline with other core kernel code.
> 
>  core/flow.c       |    5 +----
>  core/skbuff.c     |    4 +---
>  decnet/dn_route.c |    9 +++------
>  ipv4/inetpeer.c   |    5 +----
>  ipv4/ipmr.c       |    5 +----
>  ipv6/ip6_fib.c    |    4 +---
>  ipv6/route.c      |    9 +++------
>  xfrm/xfrm_input.c |    4 +---

decnet, ipv6 and xfrm can be modular, so using SLAB_PANIC there is bogus.

      parent reply	other threads:[~2004-11-14 23:11 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 ` [PATCH 7/8] " Chris Wright
2004-11-14 20:25 ` [PATCH 8/8] " Chris Wright
2004-11-14 23:11 ` Christoph Hellwig [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=20041114231101.GA9498@infradead.org \
    --to=hch@infradead.org \
    --cc=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).