Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751334AbVLMH7F (ORCPT ); Tue, 13 Dec 2005 02:59:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751324AbVLMH7F (ORCPT ); Tue, 13 Dec 2005 02:59:05 -0500 Received: from mx2.suse.de ([195.135.220.15]:52147 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S1751331AbVLMH7D (ORCPT ); Tue, 13 Dec 2005 02:59:03 -0500 Date: Tue, 13 Dec 2005 08:58:35 +0100 From: Andi Kleen To: Ingo Molnar Cc: Andrew Morton , David Howells , torvalds@osdl.org, hch@infradead.org, arjan@infradead.org, matthew@wil.cx, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org Subject: Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation Message-ID: <20051213075835.GZ15804@wotan.suse.de> References: <20051212161944.3185a3f9.akpm@osdl.org> <20051213075441.GB6765@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051213075441.GB6765@elte.hu> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 896 Lines: 20 > - i introduced a 'type-sensitive' macro wrapper that switches down() > (and the other APIs) to either to the assembly variant (if the > variable's type is struct compat_semaphore), or switches it to the new > generic mutex (if the type is struct semaphore), at build-time. There > is no runtime overhead due to this build-time-switching. Didn't that drop compatibility with 2.95? The necessary builtins are only in 3.x. Not that I'm not in favour - I would like to use C99 everywhere and it would get of the ugly spinlock workaround for i386 and x86-64 doesn't support earlier compilers anyways - but others might not agree. -Andi - 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/