Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 8 Nov 2002 12:38:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 8 Nov 2002 12:38:07 -0500 Received: from dell-paw-3.cambridge.redhat.com ([195.224.55.237]:41213 "EHLO executor.cambridge.redhat.com") by vger.kernel.org with ESMTP id ; Fri, 8 Nov 2002 12:37:00 -0500 To: Jeremy Fitzhardinge Cc: Linus Torvalds , William Lee Irwin III , "Van Maren, Kevin" , linux-ia64@linuxia64.org, Linux Kernel List , rusty@rustcorp.com.au, dhowells@redhat.com, mingo@elte.hu Subject: Re: [Linux-ia64] reader-writer livelock problem In-Reply-To: Message from Jeremy Fitzhardinge of "08 Nov 2002 09:38:25 PST." <1036777105.13021.13.camel@ixodes.goop.org> User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Date: Fri, 08 Nov 2002 17:43:35 +0000 Message-ID: <18932.1036777415@warthog.cambridge.redhat.com> From: David Howells Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 540 Lines: 14 > Do you mean have a separate lock type, or have two different read_lock > operations on the current type? You'd probably be better off with separate types... that way you can avoid problems with conditionals and also with different tracking fields being required by each grade of lock. David - 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/