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>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -mm] i386 syscall opcode reordering (pipelining)
Date: Tue, 13 Jun 2006 13:09:59 -0700	[thread overview]
Message-ID: <448F1B97.3070207@linux.intel.com> (raw)
In-Reply-To: <20060613195446.GD24167@rhlx01.fht-esslingen.de>

Andreas Mohr wrote:
> Hi all,
> 
> I'd guess that this version features improved pipeline parallelism,
> since we isolate competing %ebx accesses (_syscall4()) and
> stack push operations (_syscall5()), right?

is anybody actually EVER using those???
I would think not....

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-13 19:54 [PATCH -mm] i386 syscall opcode reordering (pipelining) Andreas Mohr
2006-06-13 20:09 ` Arjan van de Ven [this message]
2006-06-13 22:11   ` H. Peter Anvin
2006-06-13 22:15     ` David Woodhouse
2006-06-13 22:21     ` H. Peter Anvin
2006-06-14 19:28   ` Andreas Mohr

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=448F1B97.3070207@linux.intel.com \
    --to=arjan@linux.intel.com \
    --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