From: Antonio Vargas <windenntw@gmail.com>
To: Kendall Bennett <KendallB@scitechsoft.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Write Combining for PowerPC?
Date: Fri, 17 Dec 2004 22:16:19 +0100 [thread overview]
Message-ID: <69304d11041217131620036e56@mail.gmail.com> (raw)
In-Reply-To: <41B9A33A.26557.5DDD7EC8@localhost>
On Fri, 10 Dec 2004 13:23:06 -0800, Kendall Bennett
<KendallB@scitechsoft.com> wrote:
> Hi Guys,
>
> We are working on some PowerPC machines and noticed that the boxes don't
> appear to support the equivalent of Write Combining that we get on x86
> boxes. Copies to Video Memory on our Motorola Sandpoint box run about
> 10Mb/s, which is terribly, terribly slow!
>
> Does anyone know if it is possible to do something similar to Write
> Combining for the PowerPC architecture, to speed up CPU access to the
> linear framebuffer? Part of the problem is that for video overlay support
hmmm... G4 processors will do write-combining when you write two
cachelines just one after the other... there is a write-queue on the
cpu and when there is 1 write on the queue and you add another one for
the next cacheline, it will automatically merge the write. Also, if
you manage to complete a sector, then he knows you don't need to
read-then-write the memory and just issues a "kill-this-cacheline" on
the bus instead of "please-i-need-exclusive-access-for-this-cacheline"
> (not motion compensation) you have to dump the entire YUV frame into
> video memory for the hardware overlay, and even on a 1GHz PPC box playing
> an MPEG2 stream is not possible as X takes up over 80% of the CPU just to
> copy the YUV data to video memory!
>
> Obviously bus mastering will help solve this problem, but it would be
> better if there was a way to enabling faster CPU access to the
> framebuffer as well.
bus mastering is DMA-ing from system memory to gfxcard memory?
> Regards,
>
> ---
> Kendall Bennett
> Chief Executive Officer
> SciTech Software, Inc.
> Phone: (530) 894 8400
> http://www.scitechsoft.com
>
> ~ SciTech SNAP - The future of device driver technology! ~
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
--
Greetz, Antonio Vargas aka winden of network
http://wind.codepixel.com/
Las cosas no son lo que parecen, excepto cuando parecen lo que si son.
prev parent reply other threads:[~2004-12-17 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 21:23 Write Combining for PowerPC? Kendall Bennett
2004-12-17 21:16 ` Antonio Vargas [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=69304d11041217131620036e56@mail.gmail.com \
--to=windenntw@gmail.com \
--cc=KendallB@scitechsoft.com \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.