From: "David S. Miller" <davem@redhat.com>
To: ak@suse.de
Cc: alan@lxorguk.ukuu.org.uk, shemminger@osdl.org,
linux-kernel@vger.kernel.org, linux-net@vger.kernelorg
Subject: Re: [PATCH] (8/8) Kill brlock
Date: Tue, 11 Mar 2003 22:35:49 -0800 (PST) [thread overview]
Message-ID: <20030311.223549.53161356.davem@redhat.com> (raw)
In-Reply-To: <p73smtt3z7q.fsf@amdsimf.suse.de>
From: Andi Kleen <ak@suse.de>
Date: 12 Mar 2003 06:56:09 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> If Linus is scared ;) then throw them at me for -ac by all means. Anyone
> running -ac IDE test sets is brave enough to run rcu network code 8)
It's unlikely to cause problems, unless you start/stop tcpdump all day.
Protocol addition/deletion is really rare.
True, and this is why people should wrap their brains around
the patch or stress these specific cases really hard.
Rusty's module stress testers might be useful here.
next prev parent reply other threads:[~2003-03-12 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0303111644060.3002-100000@home.transmeta.com.suse.lists.linux.kernel>
[not found] ` <1047436263.20968.5.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel>
2003-03-12 5:56 ` [PATCH] (8/8) Kill brlock Andi Kleen
2003-03-12 6:35 ` David S. Miller [this message]
2003-03-10 2:33 [PATCH] small fixes in brlock.h Linus Torvalds
2003-03-12 0:15 ` [PATCH] (8/8) Kill brlock Stephen Hemminger
2003-03-12 0:23 ` David S. Miller
2003-03-12 0:31 ` Stephen Hemminger
2003-03-12 0:34 ` David S. Miller
2003-03-12 0:44 ` Linus Torvalds
2003-03-12 0:48 ` Stephen Hemminger
2003-03-12 2:31 ` Alan Cox
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=20030311.223549.53161356.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernelorg \
--cc=shemminger@osdl.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 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.