From: Luca <kronos@people.it>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Fw: framebuffer blitting performance loss 2.6.12 -> 2.6.13-rc3
Date: Sat, 30 Jul 2005 00:45:47 +0200 [thread overview]
Message-ID: <20050729224547.GA18474@dreamland.darkstar.lan> (raw)
In-Reply-To: <Pine.LNX.4.56.0507292041110.17988@pentafluge.infradead.org>
Il Fri, Jul 29, 2005 at 08:51:34PM +0100, James Simmons ha scritto:
> > Thank you for your persistence. I think I know the culprit. Someone
> > insisted on using memcpy in fb_pad_aligned_buffer(). I have already
> > fixed this before, but apparently, the memcpy was brought back. Try
> > the attached patch and let me know.
>
> Yipes, I did that. The memcpy function is suppose to be optimized for the
> platform. See string.h in the include/asm directory. I seen for example
> the Athlon would use the 3DNow instruction set to copy data. Something
> is really wrong with memcpy if moving byte by byte is faster !!!!
For small copies MMX/3DNow are not used at all. In current kernel
MMX/3DNow memcpy is used only when data size is greater than 512bytes.
Remember that MMX/3DNow uses FPU so the kernel must save/restore state
and this overhead would make the copy slow for small chunks.
Luca
--
Home: http://kronoz.cjb.net
Se il destino di un uomo e` annegare, anneghera` anche in un bicchier
d'acqua.
Proverbio yddish
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-29 22:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 10:39 Fw: framebuffer blitting performance loss 2.6.12 -> 2.6.13-rc3 Andrew Morton
2005-07-22 3:58 ` Antonino A. Daplas
2005-07-29 7:17 ` Andrew Morton
2005-07-29 14:54 ` Knut Petersen
2005-07-29 15:42 ` Antonino A. Daplas
2005-07-29 19:02 ` Andrew Morton
2005-07-29 19:52 ` James Simmons
2005-07-29 19:59 ` James Simmons
2005-07-29 19:51 ` James Simmons
2005-07-29 20:21 ` Jon Smirl
2005-07-29 22:45 ` Antonino A. Daplas
2005-08-03 17:29 ` James Simmons
2005-07-29 22:45 ` Luca [this message]
2005-07-29 20:10 ` Knut Petersen
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=20050729224547.GA18474@dreamland.darkstar.lan \
--to=kronos@people.it \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).