Re: pthread_create() slow for many threads; also time to revisit 64b context switch optimization?

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Ingo Molnar <mingo@...>
Cc: Andi Kleen <andi@...>, Ulrich Drepper <drepper@...>, Arjan van de Ven <arjan@...>, <akpm@...>, <hugh@...>, <linux-mm@...>, <linux-kernel@...>, <briangrant@...>, <cgd@...>, <mbligh@...>, Linus Torvalds <torvalds@...>, Thomas Gleixner <tglx@...>, H. Peter Anvin <hpa@...>
Date: Friday, August 15, 2008 - 9:33 am

On Fri, Aug 15, 2008 at 02:43:50PM +0200, Ingo Molnar wrote:

I used them as 64bit machines and they weren't painful at all.


MAP_32BIT was not actually added for this originally. It 
was originally added for the X server's old dynamic loader, which
needed 2GB memory.

It's main failing, which I freely admit, was to not call it MAP_31BIT.


Not sure what the semantics of that would be. For me it would
seem ugly to hardcode specific semantics in the kernel for this
("mechanism not policy")

But for most possible semantics I can think of the data structure would still 
need to be fixed I think.


IMHO the correct solution is to fix the data structure to not have such
a bad complexity in this corner case. We typically do this for all
other data structures as we discover such cases. No reason the VMAs
should be any different. 

-Andi

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: pthread_create() slow for many threads; also time to rev..., Andi Kleen, (Fri Aug 15, 9:33 am)