linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Ulrich Drepper <drepper@redhat.com>,
	Arjan van de Ven <arjan@infradead.org>,
	akpm@linux-foundation.org, hugh@veritas.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, briangrant@google.com,
	cgd@google.com, mbligh@google.com,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: pthread_create() slow for many threads; also time to revisit 64b context switch optimization?
Date: Wed, 13 Aug 2008 22:42:48 +0200	[thread overview]
Message-ID: <87fxp8zlx3.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080813151007.GA8780@elte.hu> (Ingo Molnar's message of "Wed, 13 Aug 2008 17:10:07 +0200")

Ingo Molnar <mingo@elte.hu> writes:
>
> i find it pretty unacceptable these days that we limit any aspect of 
> pure 64-bit apps in any way to 4GB (or any other 32-bit-ish limit). 

It's not limited to 2GB, there's a fallback to >4GB of course. Ok
admittedly the fallback is slow, but it's there.

I would prefer to not slow down the P4s. There are **lots** of them in
field. And they ran 64bit still quite well. Also back then I
benchmarked on early K8 and it also made a difference there (but I
admit I forgot the numbers)

I think it would be better to fix the VM because there are
other use cases of applications who prefer to allocate in a lower area.
For example Java JVMs now widely use a technique called pointer
compression where they dynamically adjust the pointer size based
on how much memory the process uses. For that you have to get
low memory in the 47bit VM too. The VM should deal with that gracefully.

To be honest I always thought the linear search in the VMA list
was a little dumb. I'm sure there are other cases where it hurts
too. Perhaps this would be really an opportunity  to do something about it :)

-Andi

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2008-08-13 20:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <af8810200808121736q76640cc1kb814385072fe9b29@mail.gmail.com>
2008-08-13  0:45 ` Pardo
2008-08-13 10:44   ` Ingo Molnar
2008-08-13 13:35     ` Arjan van de Ven
2008-08-13 14:21       ` Ulrich Drepper
2008-08-13 14:25         ` Ingo Molnar
2008-08-13 14:36           ` Ulrich Drepper
2008-08-13 15:10             ` Ingo Molnar
2008-08-13 15:21               ` Ulrich Drepper
2008-08-13 15:40                 ` Ingo Molnar
2008-08-13 15:55                   ` Ulrich Drepper
2008-08-13 16:02                     ` Ingo Molnar
2008-08-15 15:54                       ` Jamie Lokier
2008-08-15 16:03                         ` Ingo Molnar
2008-08-15 17:13                         ` Ulrich Drepper
2008-08-15 17:19                           ` Ingo Molnar
2008-08-15 17:23                             ` Ulrich Drepper
2008-08-15 19:00                               ` Ingo Molnar
2008-08-13 17:09                     ` Linus Torvalds
2008-08-13 18:04                       ` Ulrich Drepper
2008-08-13 18:16                         ` Arjan van de Ven
2008-08-13 18:22                           ` Ulrich Drepper
2008-08-13 16:05                 ` H. Peter Anvin
2008-08-13 20:42               ` Andi Kleen [this message]
2008-08-13 20:56                 ` Andrew Morton
2008-08-13 21:46                   ` Andi Kleen
2008-08-15 12:43                 ` Ingo Molnar
2008-08-15 13:33                   ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fxp8zlx3.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=briangrant@google.com \
    --cc=cgd@google.com \
    --cc=drepper@redhat.com \
    --cc=hpa@zytor.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@google.com \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox