From: Arjan van de Ven <arjan@infradead.org>
To: Marcelo Tosatti <marcelo@kvack.org>
Cc: Dave Jones <davej@redhat.com>,
Jordan Crouse <jordan.crouse@amd.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use movntq version of fast_clear_page/fast_copy_page on Geode
Date: Wed, 14 Feb 2007 22:23:28 +0100 [thread overview]
Message-ID: <1171488209.12771.463.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20070214201736.GA5794@dmt.lan>
On Wed, 2007-02-14 at 18:17 -0200, Marcelo Tosatti wrote:
> On Wed, Feb 14, 2007 at 02:55:46PM -0500, Dave Jones wrote:
> > On Wed, Feb 14, 2007 at 05:08:39PM -0200, Marcelo Tosatti wrote:
> > >
> > > movntq instruction is supported by Geode CPU's, so use
> > > fast_clear_page/fast_copy_page versions that have it.
> >
> > it's supported, but is it a win ?
> > The same was also true of the VIA C3/C7's, but due to
> > poor memory bandwidth, it turned out to be slower in most cases.
>
> Do you have the numbers for VIA C3/C7 around?
>
> The Geode benefits from movntq instead of movq:
>
> [marcelo@localhost ~]$ cat /proc/cpuinfo
> processor : 0
> vendor_id : Geode by NSC
> cpu family : 5
> model : 5
> model name : Geode(TM) Integrated Processor by National Semi
> stepping : 2
> cpu MHz : 364.898
> cache size : 32 KB
> ...
>
> [marcelo@localhost ~]$ wget http://www.fenrus.demon.nl/athlon.c
> ...
btw there is a caveat with this program: you don't see that this evicts
the data RIGHT AFTER THE COPY, so if you use it again you pay AGAIN the
memory bandwidth price...
next prev parent reply other threads:[~2007-02-14 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 19:08 Marcelo Tosatti
2007-02-14 19:55 ` Dave Jones
2007-02-14 20:17 ` Marcelo Tosatti
2007-02-14 20:47 ` Dave Jones
2007-02-14 21:23 ` Arjan van de Ven [this message]
2007-02-14 21:16 ` Alan
2007-02-15 15:01 ` Marcelo Tosatti
2007-02-14 19:17 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=1171488209.12771.463.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=jordan.crouse@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.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
all inboxes | Powered by JetHome®