![]() | |||||||||||||
Messages in this thread |
> > It may well make sense for the O(1) scheduler to be inlining this.
>
> Why?
I was thinking that perhaps this call was in a certain critical
performance path of the O(1) scheduler.
Turned out it wasn't - see further Nick Piggin's followups to this
same thread.
My latest bitmap/cpumask patch moves this out of line, for ia64.
The other arch's that use this large find_next_bit() code might
want to move it out too.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
-
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/
| ||||||||||||
| Last update: 2005-03-22 13:02 [from the cache] ©2003-2008 | |||||||||||||