Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Michael Sundius <msundius@cisco.com>,
	linux-mips@linux-mips.org, "VomLehn, David" <dvomlehn@cisco.com>,
	msundius@sundius.com
Subject: Re: memcpy and prefetch
Date: Wed, 28 Jan 2009 10:37:53 +0000	[thread overview]
Message-ID: <20090128103753.GC2234@linux-mips.org> (raw)
In-Reply-To: <497F93C1.3090401@caviumnetworks.com>

On Tue, Jan 27, 2009 at 03:07:45PM -0800, David Daney wrote:

> The Cavium OCTEON port overrides the default memcpy and does use  
> prefetch.  It was recently merged (2.6.29-rc2).  Look at octeon-memcpy.S
>
> I have thought that memcpy could be generated by mm/page.c as copy_page  
> and clear_page are.

No, these two only generate copy_page and clear_page.  I and Thiemo were
considering to extend this to a full memcopy however.

  Ralf

  reply	other threads:[~2009-01-28 10:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 23:00 memcpy and prefetch Michael Sundius
2009-01-27 23:07 ` David Daney
2009-01-28 10:37   ` Ralf Baechle [this message]
2009-01-28 15:28     ` Atsushi Nemoto
2009-01-28 18:30       ` Ralf Baechle
2009-01-29 12:36         ` Atsushi Nemoto
2009-01-29 15:58           ` Ralf Baechle
2009-01-30  3:39             ` David VomLehn (dvomlehn)
2009-01-30  3:39               ` David VomLehn (dvomlehn)
2009-02-04 21:27               ` Ralf Baechle
2009-02-04 21:27                 ` Ralf Baechle
2009-02-05 15:31                 ` Atsushi Nemoto
2009-01-28 19:28   ` Michael Sundius
2009-01-28 19:54     ` David Daney
2009-01-28 21:52       ` Chad Reese

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=20090128103753.GC2234@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ddaney@caviumnetworks.com \
    --cc=dvomlehn@cisco.com \
    --cc=linux-mips@linux-mips.org \
    --cc=msundius@cisco.com \
    --cc=msundius@sundius.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