Date: Fri, 9 Apr 2004 10:53:49 -0700
From: Paul Jackson <pj@sgi.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: colpatch@us.ibm.com, wli@holomorphy.com, linux-kernel@vger.kernel.org
Subject: Re: [Patch 17/23] mask v2 = [6/7] nodemask_t_ia64_changes
Message-Id: <20040409105349.6b40fe02.pj@sgi.com>
In-Reply-To: <200404091054.24618.vda@port.imtp.ilyichevsk.odessa.ua>
References: <20040401122802.23521599.pj@sgi.com>
	<20040406235000.6c06af9a.pj@sgi.com>
	<20040407004437.3a078f28.pj@sgi.com>
	<200404091054.24618.vda@port.imtp.ilyichevsk.odessa.ua>
Organization: SGI
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 856
Lines: 23

> > 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/