Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261262AbTEHJqi (ORCPT ); Thu, 8 May 2003 05:46:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261265AbTEHJqi (ORCPT ); Thu, 8 May 2003 05:46:38 -0400 Received: from wsip-68-15-8-100.sd.sd.cox.net ([68.15.8.100]:64390 "EHLO gnuppy") by vger.kernel.org with ESMTP id S261262AbTEHJqg (ORCPT ); Thu, 8 May 2003 05:46:36 -0400 Date: Thu, 8 May 2003 02:59:11 -0700 To: Ming Lei Cc: linux-kernel@vger.kernel.org, "Bill Huey (Hui)" Subject: Re: linux rt priority thread corrupt global variable? Message-ID: <20030508095911.GA20934@gnuppy.monkey.org> References: <029601c31540$b57f1280$0305a8c0@arch.sel.sony.com> <20030508095238.GA20844@gnuppy.monkey.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030508095238.GA20844@gnuppy.monkey.org> User-Agent: Mutt/1.5.4i From: Bill Huey (Hui) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 890 Lines: 21 On Thu, May 08, 2003 at 02:52:38AM -0700, Bill Huey wrote: > No, it's not a fully preemptive kernel, but spreads preemption points > throughout the source tree, both directly and indirectly, instead. Spinlocks > are the primary mutex of choice in Linux and create atomic critical sections > that can't be preempted with respect to the normal Linux scheduler. Fully Geez, this isn't exactly right either, my brain is failing me at the moment. > preemptive systems tend to use sleepable locks with relaxed preemptability > within critical sections and add the possible option of priority inheritance > depending on the system. /me thinks bill - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/