Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751106AbWCaA6f (ORCPT ); Thu, 30 Mar 2006 19:58:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751102AbWCaA6e (ORCPT ); Thu, 30 Mar 2006 19:58:34 -0500 Received: from omx1-ext.sgi.com ([192.48.179.11]:33993 "EHLO omx1.americas.sgi.com") by vger.kernel.org with ESMTP id S1751106AbWCaA6d (ORCPT ); Thu, 30 Mar 2006 19:58:33 -0500 Date: Thu, 30 Mar 2006 16:58:25 -0800 (PST) From: Christoph Lameter To: "Luck, Tony" cc: David Mosberger-Tang , Nick Piggin , Zoltan Menyhart , "Boehm, Hans" , "Grundler, Grant G" , "Chen, Kenneth W" , akpm@osdl.org, linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org Subject: RE: Synchronizing Bit operations V2 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 820 Lines: 17 On Thu, 30 Mar 2006, Luck, Tony wrote: > > Also some higher level functions may want to have the mode passed to them > > as parameters. See f.e. include/linux/buffer_head.h. Without the > > parameters you will have to maintain farms of definitions for all cases. > > But if any part of the call chain from those higher level functions > down to these low level functions is not inline, then the compiler > won't be able to collapse out the "switch (mode)" ... so we'd end up > with a ton of extra object code. Correct. But such bitops are typically defined to be inline. - 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/