public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] i386 usercopy.c opcode reordering (pipelining)
Date: Tue, 13 Jun 2006 13:10:54 -0700	[thread overview]
Message-ID: <448F1BCE.50708@linux.intel.com> (raw)
In-Reply-To: <20060613195502.GE24167@rhlx01.fht-esslingen.de>

Andreas Mohr wrote:
> Hi all,
> 
> this one wrote to register %0 and immediately right-shifted it,
> so let's andl register %3 first for better parallelism (rrright?).

have you benchmarked this?
I would actually expect no difference since a reg-reg move is basically
a thing for the register rename engine which then... well it's supposed
to be near free like this.

      reply	other threads:[~2006-06-13 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-13 19:55 [PATCH -mm] i386 usercopy.c opcode reordering (pipelining) Andreas Mohr
2006-06-13 20:10 ` Arjan van de Ven [this message]

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=448F1BCE.50708@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=andi@rhlx01.fht-esslingen.de \
    --cc=linux-kernel@vger.kernel.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