From: Manfred Spraul <manfred@colorfullife.com>
To: Arjan van de Ven <arjan@fenrus.demon.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sse for fast_clear_page()?
Date: Thu, 08 Feb 2001 19:36:34 +0100 [thread overview]
Message-ID: <3A82E732.4229045F@colorfullife.com> (raw)
In-Reply-To: <m14Qv0z-000OaDC@amadeus.home.nl>
Arjan van de Ven wrote:
>
> In article <3A82D325.9068BC07@colorfullife.com> you wrote:
> > fast_clear_page() uses mmx instructions for clearing a page, what about
> > using sse instructions?
> > sse instructions can store 128 bit in one instruction, mmx only 64 bit.
>
> the sse FP registers might be lossy.
I thought that too, thus I only implemented memset(,0,) with sse.
But then I found this document on Intel website:
http://developer.intel.com/software/idap/media/pdf/copy.pdf
Intel recommends using sse registers for generic memcopy - they can't be
lossy.
> On my athlon, the in-kernel mmx
> functions are memory-bound (eg > 1 Gbyte/sec throughput)
>
You are using an Athlon with SDRAM?
A Pentium 4 has a 3.2 GB memory bus and I saw a benchmark that compared
mmx and sse memmove, and sse was _much_ faster.
I've implemented a user space sse copy_page, and:
* mmx is the slowest version! (~12000 cpu ticks/page).
* movsd is slightly faster (~11850 cpu ticks/page). Probably due to the
special 'rep movsd' optimization in the Pentium III (cpu notices that
ecx is large and switches to a cache line copy mode).
* sse is the fastest version (~ 11500 cpu ticks/page)
Everything with cold caches.
> Userspace program for the athlon code:
>
> http://www.fenrus.demon.nl/athlon.c
>
I'll check it.
--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-08 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 17:11 sse for fast_clear_page()? Manfred Spraul
2001-02-08 17:37 ` Arjan van de Ven
2001-02-08 18:36 ` Manfred Spraul [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=3A82E732.4229045F@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=arjan@fenrus.demon.nl \
--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