From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Hugh Dickins <hugh@veritas.com>,
William Lee Irwin III <wli@movementarian.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: pud_bad vs pud_bad
Date: Thu, 05 Feb 2009 16:08:31 -0800 [thread overview]
Message-ID: <498B7F7F.3090701@goop.org> (raw)
In-Reply-To: <20090205234241.GA14203@elte.hu>
Ingo Molnar wrote:
> just the act of using PAE was measured to cause multi-percent slowdown in
> fork() and exec() latencies, etc. The pagetables are twice as large so is
> that really surprising?
>
Is there a similar slowdown running the CPU in 32 vs 64 bit mode? Or
does having more/wider registers mitigate it?
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Hugh Dickins <hugh@veritas.com>,
William Lee Irwin III <wli@movementarian.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: pud_bad vs pud_bad
Date: Thu, 05 Feb 2009 16:08:31 -0800 [thread overview]
Message-ID: <498B7F7F.3090701@goop.org> (raw)
In-Reply-To: <20090205234241.GA14203@elte.hu>
Ingo Molnar wrote:
> just the act of using PAE was measured to cause multi-percent slowdown in
> fork() and exec() latencies, etc. The pagetables are twice as large so is
> that really surprising?
>
Is there a similar slowdown running the CPU in 32 vs 64 bit mode? Or
does having more/wider registers mitigate it?
J
--
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>
next prev parent reply other threads:[~2009-02-06 0:08 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 18:23 pud_bad vs pud_bad Jeremy Fitzhardinge
2009-02-05 18:23 ` Jeremy Fitzhardinge
2009-02-05 18:43 ` Ingo Molnar
2009-02-05 18:43 ` Ingo Molnar
2009-02-05 18:54 ` Jeremy Fitzhardinge
2009-02-05 18:54 ` Jeremy Fitzhardinge
2009-02-05 19:10 ` Ingo Molnar
2009-02-05 19:10 ` Ingo Molnar
2009-02-05 19:26 ` Jeremy Fitzhardinge
2009-02-05 19:26 ` Jeremy Fitzhardinge
2009-02-05 19:31 ` Ingo Molnar
2009-02-05 19:31 ` Ingo Molnar
2009-02-05 19:38 ` Hugh Dickins
2009-02-05 19:38 ` Hugh Dickins
2009-02-05 19:49 ` Ingo Molnar
2009-02-05 19:49 ` Ingo Molnar
2009-02-05 19:58 ` wli
2009-02-05 19:58 ` wli
2009-02-05 20:14 ` Hugh Dickins
2009-02-05 20:14 ` Hugh Dickins
2009-02-05 20:56 ` wli
2009-02-05 20:56 ` wli
2009-02-05 21:09 ` Hugh Dickins
2009-02-05 21:09 ` Hugh Dickins
2009-02-05 20:12 ` Hugh Dickins
2009-02-05 20:12 ` Hugh Dickins
2009-02-05 20:42 ` Jeremy Fitzhardinge
2009-02-05 20:42 ` Jeremy Fitzhardinge
2009-02-05 20:51 ` Hugh Dickins
2009-02-05 20:51 ` Hugh Dickins
2009-02-05 21:05 ` Jeremy Fitzhardinge
2009-02-05 21:05 ` Jeremy Fitzhardinge
2009-02-05 21:50 ` Ingo Molnar
2009-02-05 21:50 ` Ingo Molnar
2009-02-05 22:07 ` Jeremy Fitzhardinge
2009-02-05 22:07 ` Jeremy Fitzhardinge
2009-02-05 23:42 ` Ingo Molnar
2009-02-05 23:42 ` Ingo Molnar
2009-02-06 0:08 ` Jeremy Fitzhardinge [this message]
2009-02-06 0:08 ` Jeremy Fitzhardinge
2009-02-06 0:50 ` Ingo Molnar
2009-02-06 0:50 ` Ingo Molnar
2009-02-05 20:57 ` Ingo Molnar
2009-02-05 20:57 ` Ingo Molnar
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=498B7F7F.3090701@goop.org \
--to=jeremy@goop.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=wli@movementarian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.