Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266884AbUIORLE (ORCPT ); Wed, 15 Sep 2004 13:11:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266626AbUIORIx (ORCPT ); Wed, 15 Sep 2004 13:08:53 -0400 Received: from sweetums.bluetronic.net ([24.199.150.42]:30923 "EHLO sweetums.bluetronic.net") by vger.kernel.org with ESMTP id S266646AbUIOREq (ORCPT ); Wed, 15 Sep 2004 13:04:46 -0400 Date: Wed, 15 Sep 2004 13:04:11 -0400 (EDT) From: Ricky Beam To: Ingo Molnar cc: Linux Kernel Mail List Subject: Re: [patch] remove the BKL (Big Kernel Lock), this time for real In-Reply-To: <20040915155555.GA11019@elte.hu> Message-ID: 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: 712 Lines: 18 On Wed, 15 Sep 2004, Ingo Molnar wrote: >yes, but progress in this area seems to have slowed down, and people are >hurting from the latencies introduced by the BKL meanwhile. Who cares if >some rare big chunk of code runs under a semaphore, as long as it's >preemptable? "as long as it's preemptable" is the key there. Not all arch's can run with PREEMPT enabled (yet) -- sparc/sparc64 for but one. And at the moment, PREEMPT is a bit on the hosed side. --Ricky - 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/