Newsgroups: fa.linux.kernel
Return-Path: <>
From: Rusty Russell <>
Subject: [PATCH] 2.5.1-pre11 Read-Copy-Update Patch 
Original-Date: 	Fri, 14 Dec 2001 22:27:14 +1100
Original-Message-Id: <>
Precedence: bulk
Organization: Internet mailing list
Date: Fri, 14 Dec 2001 12:27:56 GMT
Message-ID: <>
Lines: 566

Hi Linus,

	The hotplug CPU patch needs read-copy-update, otherwise
everyone has to lock around references to smp_num_cpus.  By waiting
until everyone has scheduled, we cleanly implement two-stage CPU

	Now, this patch is (obviously) currently a NOOP on UP: with
preemption on UP this would change.  Are you intending to implement
preemption in 2.5, and if so, for UP or SMP?

	My module loader replacement also uses RCU, to ensure noone is
still inside the module.  Otherwise we continue down the current path,
and force every registration interface in the kernel to lock on entry,
unlock on exit.  (If you want this, it's then a fairly short hop to a

	I'd love to know if I should implement RCU-with-preemption on
UP, abandon the RCU approach, or send my patches as is.


Hotplug CPU:

New module loader:


  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

			  SCO's Case Against IBM

November 12, 2003 - Jed Boal from Eyewitness News KSL 5 TV provides an
overview on SCO's case against IBM. Darl McBride, SCO's president and CEO,
talks about the lawsuit's impact and attacks. Jason Holt, student and 
Linux user, talks about the benefits of code availability and the merits 
of the SCO vs IBM lawsuit. See SCO vs IBM.

Note: The materials and information included in these Web pages are not to
be used for any other purpose other than private study, research, review
or criticism.