The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: ling.ma@intel.com
Cc: hpa@zytor.com, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC V2] [x86] Optimize copy-page by reducing impact from HW prefetch
Date: Thu, 23 Jun 2011 16:34:42 +0200	[thread overview]
Message-ID: <20110623143442.GA14680@elte.hu> (raw)
In-Reply-To: <1308353053-1928-1-git-send-email-ling.ma@intel.com>


* ling.ma@intel.com <ling.ma@intel.com> wrote:

> ---
>  arch/x86/lib/copy_page_64.S |  124 +++++++++++++++++++-----------------------
>  1 files changed, 56 insertions(+), 68 deletions(-)

What happened to the 2 patches suggestion i made in my mail:

> and do this cleanup patch first and the speedup on top of it, and
> keep the two in two separate patches so that the modification to the
> assembly code can be reviewed more easily.

?

Thanks,

	Ingo

      parent reply	other threads:[~2011-06-23 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 23:24 [PATCH RFC V2] [x86] Optimize copy-page by reducing impact from HW prefetch ling.ma
2011-06-20  3:42 ` Ma, Ling
2011-06-23 14:34 ` Ingo Molnar [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=20110623143442.GA14680@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=ling.ma@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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