Date: Fri, 23 Feb 2001 12:10:05 +0100
From: Dipankar Sarma <dipan...@sequent.com>
Subject: Read-Copy Update mutual exclusion for linux
Message-ID: <20010223163600.B26060@in.ibm.com>
Reply-To: dipan...@sequent.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: robo...@news.nic.it
X-Mailing-List: linux-kernel@vger.kernel.org
Approved: robo...@news.nic.it (1.20)
NNTP-Posting-Host: 33060.anti-phl.bofh.it
Newsgroups: linux.kernel
Organization: linux.*_mail_to_news_unidirectional_gateway
Path: supernews.google.com!sn-xit-03!supernews.com!bofh.it!robomod
X-Original-Cc: linux-ker...@vger.kernel.org
X-Original-Date: Fri, 23 Feb 2001 16:36:00 +0530
X-Original-Sender: linux-kernel-ow...@vger.kernel.org
X-Original-To: lse-t...@lists.sourceforge.net
Lines: 24

Read-Copy Update is a two-phase mutual exclusion method that can be
used to avoid overhead and code complexity of conventional methods
that use spin-waiting. It uses the event-driven nature of operating
systems to defer exceptional conditions until currently active code
has completed allowing common code paths to proceed without delay.
This technique is potentially useful for maintenance of read-mostly
data structures and unusual situations like module unloading.

An implementation of this based on the original DYNIX/ptx implementation 
is now available for Linux (2.4.1 kernel) at 
http://lse.sourceforge.net/locking/rclock.html.

Thanks
Dipankar

-- 
Dipankar Sarma  (dipan...@sequent.com)
IBM Linux Technology Center
IBM India Software Lab, Bangalore, India.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Path: supernews.google.com!sn-xit-03!supernews.com!logbridge.uoregon.edu!news.maxwell.syr.edu!newshub2.home.com!news.home.com!newshub1-work.home.com!gehenna.pell.portland.or.us!nntp-server.caltech.edu!nntp-server.caltech.edu!mail2news96
Newsgroups: mlist.linux.kernel
Date: 	Thu, 8 Mar 2001 17:14:07 +0530
From: Maneesh Soni <smane...@in.ibm.com>
X-To: lse tech <lse-t...@lists.sourceforge.net>
X-Cc: lkml <linux-ker...@vger.kernel.org>, Andi Kleen <a...@suse.de>,
        Keith Owens <k...@ocs.com.au>, Rusty Russell <ru...@linuxcare.com.au>,
        Mortan Andrew Mortan <andr...@uow.edu.au>,
        "A. N. Kuznetsov" <kuz...@ms2.inr.ac.ru>,
        Miller David Miller <da...@redhat.com>
Subject: [Patch] Module Unloading using Read-Copy-Update
Message-ID: <linux.kernel.20010308171407.A5594@in.ibm.com>
Reply-To: smane...@in.ibm.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Approved: n...@nntp-server.caltech.edu
Lines: 29


Hello,
 
In this post I would like to submit a patch providing a two phase cleanup logic
for solving the module unloading races in linux. It uses the deferred update
interface provided by the Read-Copy-Update mechanism. A patch with 
implementation of Read-Copy-Update on linux has been posted earlier on lkml and 
lse-tech by Dipankar Sarma
   http://marc.theaimsgroup.com/?l=lse-tech&m=98292649600654&w=2
 
In this first version of the new cleanup logic, I have tried to keep the changes 
lesser. Please download the patch and a readme along with a few testcases from
 
   http://lse.sourceforge.net/locking/module_unloading-2.4.1-0.1.tar.gz
 
 
Thank you,
Maneesh
 
--
Maneesh Soni
Linux Technology Center,
IBM Software Labs, Bangalore, INDIA
Phone: +91-80-5262355 Extn: 2717                                                 
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

			  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.