From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754948Ab1I3P0J (ORCPT ); Fri, 30 Sep 2011 11:26:09 -0400 Received: from casper.infradead.org ([85.118.1.10]:53024 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752980Ab1I3P0I convert rfc822-to-8bit (ORCPT ); Fri, 30 Sep 2011 11:26:08 -0400 Subject: Re: [RFC][PATCH 2/5] signal: Add rwlock to protect sighand->action From: Peter Zijlstra To: Matt Fleming Cc: Oleg Nesterov , Tejun Heo , linux-kernel@vger.kernel.org, Tony Luck , Matt Fleming , Thomas Gleixner , Anirudh Badam Date: Fri, 30 Sep 2011 17:25:17 +0200 In-Reply-To: <1317395577-14091-3-git-send-email-matt@console-pimps.org> References: <1317395577-14091-1-git-send-email-matt@console-pimps.org> <1317395577-14091-3-git-send-email-matt@console-pimps.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Mailer: Evolution 3.0.3- Message-ID: <1317396317.12973.5.camel@twins> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2011-09-30 at 16:12 +0100, Matt Fleming wrote: > > As sighand->action is read much more frequently than written a rwlock > makes the most sense here. Ha! you would think so, but then you'd forget that read_lock()+read_unlock() are atomic ops modifying the lock state as well. Furthermore rwlocks aren't fair by any means. Therefore rwlock_t should never be used, use a spinlock_t possibly in combination with RCU or seqcount etc..