Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262410AbVCJJyq (ORCPT ); Thu, 10 Mar 2005 04:54:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262489AbVCJJyq (ORCPT ); Thu, 10 Mar 2005 04:54:46 -0500 Received: from cpe-24-94-57-164.stny.res.rr.com ([24.94.57.164]:3223 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id S262410AbVCJJym (ORCPT ); Thu, 10 Mar 2005 04:54:42 -0500 Date: Thu, 10 Mar 2005 04:54:41 -0500 (EST) From: Steven Rostedt X-X-Sender: rostedt@localhost.localdomain Reply-To: rostedt@goodmis.org To: Lee Revell cc: Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: [patch] Real-Time Preemption, -RT-2.6.11-rc3-V0.7.38-01 In-Reply-To: Message-ID: References: <20050204100347.GA13186@elte.hu> <1108789704.8411.9.camel@krustophenia.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 709 Lines: 18 On Thu, 10 Mar 2005, Steven Rostedt wrote: > The short term fix is probably to put back the preempt_disables, the long > term is to get rid of these stupid bit_spin_lock busy loops. > Doing a quick search on the kernel, it looks like only kjournald uses the bit_spin_locks. I'll start converting them to spinlocks. The use seems to be more of a hack, since it is using bits in the state field for locking, and these bits aren't used for anything else. -- Steve - 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/