[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090107131846.GF3529@elte.hu>
Date: Wed, 7 Jan 2009 14:18:46 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Hugh Dickins <hugh@...itas.com>
Cc: Andi Kleen <andi@...stfloor.org>,
Andrew Morton <akpm@...ux-foundation.org>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [3/5] Mark complex bitops.h inlines as __always_inline
* Hugh Dickins <hugh@...itas.com> wrote:
> Hugh Dickins noticed that released gcc versions building the kernel with
> CONFIG_OPTIMIZE_INLINING=y don't inline some of the bitops - sometimes
> generating very inefficient pageflag tests, and many instances of
> constant_test_bit().
Could you quantify that please?
We really dont want to reintroduce __always_inline just for performance /
code size reasons. If GCC messes up and makes a larger / more inefficient
kernel, GCC will be fixed. CONFIG_OPTIMIZE_INLINING is default-off, so
enable it only if it improves your kernel.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists