From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] Enabled building of x86_64 code on Mac OS X
Date: Tue, 27 Jan 2009 00:59:20 +0000 [thread overview]
Message-ID: <200901270059.21958.paul@codesourcery.com> (raw)
In-Reply-To: <20090127004232.GE9296@shareable.org>
On Tuesday 27 January 2009, Jamie Lokier wrote:
> Paul Brook wrote:
> > > Out of curiousity, what are the benefits of using 64-bit apps in OS X?
> >
> > My guess is that same as most other x86 targets: The i386 legacy
> > mode is crippled by lack of registers, modern x86 hardware has a big
> > fat wide memory bus, and noone's bothered implementing an ILP32
> > 64-bit API[1], so 64-bit apps give measurably better overall
> > performance.
>
> Except they use more memory and memory bandwidth (arguably filling
> nearly half of it with zeros most of the time :-) so worse overall
> performance in some cases.
I did say overall performance.
My experience with AMD hardware is that you generally get ~10% overall
improvement from LP64. Intel hardware (particularly the early 64-bit cores)
less so, but it's generally still a win.
I guess ILP32 long mode would probably increase that further, and avoid the
odd regressions. It's an awful lot of work to implement though, especially on
a target that isn't used to having lots of incompatible variants.
Paul
next prev parent reply other threads:[~2009-01-27 1:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 19:44 [Qemu-devel] [PATCH] Enabled building of x86_64 code on Mac OS X Alexander Graf
2009-01-26 15:40 ` Anthony Liguori
2009-01-27 0:34 ` Paul Brook
2009-01-27 0:42 ` Jamie Lokier
2009-01-27 0:59 ` Paul Brook [this message]
2009-01-27 1:22 ` Anthony Liguori
2009-01-27 9:21 ` Alexander Graf
2009-01-27 14:37 ` Jamie Lokier
2009-01-27 15:00 ` Laurent Desnogues
2009-01-27 0:40 ` C.W. Betts
2009-01-27 0:40 ` C.W. Betts
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=200901270059.21958.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.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.