Messages in this thread | | | Date | Wed, 5 Jul 2006 13:12:40 -0400 | From | Chuck Ebbert <> | Subject | Re: [patch] uninline init_waitqueue_*() functions |
| |
In-Reply-To: <20060705102633.GA17975@elte.hu>
On Wed, 5 Jul 2006 12:26:33 +0200, Ingo Molnar wrote:
> The rough rule of thumb for inlining is that anything that is larger > than one C statement is probably too large for inlining. (but even > 1-line statements might be too fat at times)
x86-64 software optimization guide says:
For functions that create fewer than 25 machine instructions once inlined, it is likely that the function call overhead is close to, or more than, the time spent executing the function body. In these cases, function inlining is recommended.
Of course you need to consider whether the code is speed-critical to begin with.
-- Chuck "You can't read a newspaper if you can't read." --George W. Bush - 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/
| |