From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752286AbZHAAmj (ORCPT ); Fri, 31 Jul 2009 20:42:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752113AbZHAAmi (ORCPT ); Fri, 31 Jul 2009 20:42:38 -0400 Received: from e1.ny.us.ibm.com ([32.97.182.141]:45784 "EHLO e1.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752076AbZHAAmh (ORCPT ); Fri, 31 Jul 2009 20:42:37 -0400 Message-ID: <4A738F78.9020106@us.ibm.com> Date: Fri, 31 Jul 2009 17:42:32 -0700 From: Darren Hart User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: Frederic Weisbecker CC: Thomas Gleixner , LKML , rt-users , Ingo Molnar , Steven Rostedt , Peter Zijlstra , Carsten Emde , Clark Williams , Frank Rowand , Robin Gareus , Gregory Haskins , Philippe Reynes , Fernando Lopez-Lezcano , Will Schmidt , Jan Blunck , Sven-Thorsten Dietrich , Jon Masters Subject: Re: [ANNOUNCE] 2.6.31-rc4-rt1 References: <20090731232205.GA7574@nowhere> In-Reply-To: <20090731232205.GA7574@nowhere> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Frederic Weisbecker wrote: > On Thu, Jul 30, 2009 at 02:48:04AM +0200, Thomas Gleixner wrote: >> Further plans: >> >> 1) We seriously want to tackle the elimination of the PREEMPT_RT >> annoyance #1, aka BKL. The Big Kernel Lock is still used in ~330 >> files all across the kernel. A lot of work has been done already to >> push down the lock into the code which still thinks it needs to be >> protected by it. Some work has been done already in the (a little >> bit stale) kill-the-BKL and core/kill-the-BKL branches of the -tip >> git tree. If you want to help, please check those branches whether >> the code has been tackled already or not to avoid redundant >> work. If you decide to take care of one please note it on: >> >> http://rt.wiki.kernel.org/index.php/Big_Kernel_Lock > > > We (I) can't write to this file :) > > However, I'll try to attack the remaining bkl that resides in tty... I took a look at the perms, then the history - looks like you sorted it out. -- Darren Hart IBM Linux Technology Center Real-Time Linux Team