Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755226Ab0KMWvu (ORCPT ); Sat, 13 Nov 2010 17:51:50 -0500 Received: from canuck.infradead.org ([134.117.69.58]:34685 "EHLO canuck.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754348Ab0KMWvt convert rfc822-to-8bit (ORCPT ); Sat, 13 Nov 2010 17:51:49 -0500 Subject: Re: Kernel rwlock design, Multicore and IGMP From: Peter Zijlstra To: Cypher Wu Cc: linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Sat, 13 Nov 2010 23:52:03 +0100 Message-ID: <1289688723.2109.396.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 630 Lines: 13 On Thu, 2010-11-11 at 21:49 +0800, Cypher Wu wrote: > I'm using TILEPro and its rwlock in kernel is a liitle different than > other platforms. It have a priority for write lock that when tried it > will block the following read lock even if read lock is hold by > others. That's a bug, rwlock_t must most definitely be a read preference lock, there's tons of code depending on that. -- 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/