From: Arjan van de Ven <arjanv@redhat.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: akpm@osdl.org, "Martin J. Bligh" <mbligh@aracnet.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] shrink per_cpu_pages to fit 32byte cacheline
Date: Tue, 14 Sep 2004 13:44:12 +0200 [thread overview]
Message-ID: <20040914114412.GC21362@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040914100152.GB23935@logos.cnet>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
On Tue, Sep 14, 2004 at 07:01:52AM -0300, Marcelo Tosatti wrote:
> On Tue, Sep 14, 2004 at 01:13:29PM +0200, Arjan van de Ven wrote:
> > On Tue, Sep 14, 2004 at 06:34:07AM -0300, Marcelo Tosatti wrote:
> > > How come short access can cost 1 extra cycle? Because you need two "read bytes" ?
> >
> > on an x86, a word (2byte) access will cause a prefix byte to the
> > instruction, that particular prefix byte will take an extra cycle during execution
> > of the instruction and potentially reduces the parallal decodability of
> > instructions....
>
> OK thanks Arjan, where did you read this? The "Intel IA32 Optimization Guide" ?
some version of that; I can't find it in my current one though. Hrmpf
Maybe there's someone from intel or amd on this list who can confirm the
performance impact of the 0x66 operand size override prefix
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-14 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 23:38 Marcelo Tosatti
2004-09-14 6:10 ` Arjan van de Ven
2004-09-14 9:34 ` Marcelo Tosatti
2004-09-14 11:13 ` Arjan van de Ven
2004-09-14 10:01 ` Marcelo Tosatti
2004-09-14 11:44 ` Arjan van de Ven [this message]
2004-09-14 22:45 ` Marcelo Tosatti
2004-09-15 0:57 ` Nick Piggin
2004-09-15 0:48 ` Marcelo Tosatti
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=20040914114412.GC21362@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=mbligh@aracnet.com \
/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