home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.ibm.pc.hardware:21754 comp.sys.intel:1490 comp.sys.ibm.pc.misc:11445
- Newsgroups: comp.sys.ibm.pc.hardware,comp.sys.intel,comp.sys.ibm.pc.misc
- Path: sparky!uunet!mcsun!Germany.EU.net!news.netmbx.de!zrz.tu-berlin.de!math.fu-berlin.de!news.th-darmstadt.de!adams
- From: adams@pdv3.fmr.maschinenbau.th-darmstadt.de (Hans Adams)
- Subject: Re: More on Local Bus - What about Unix?? S3 vs.
- Sender: news@news.th-darmstadt.de (The Usenet-News System)
- Message-ID: <ADAMS.92Aug13163126@pdv3.pdv3.fmr.maschinenbau.th-darmstadt.de>
- In-Reply-To: roell@informatik.tu-muenchen.de's message of Thu, 13 Aug 1992 06: 41:56 GMT
- Date: Thu, 13 Aug 1992 16:31:26 GMT
- References: <0105010F.ac48r9@mprnews.mpr.com>
- <1992Aug10.092255.118@vulcan.resmel.bhp.com.au>
- <Bss82v.LJM@usenet.ucs.indiana.edu>
- <ADAMS.92Aug13004812@PDV2.pdv2.fmr.maschinenbau.th-darmstadt.de>
- <1992Aug13.064156.2539@Informatik.TU-Muenchen.DE>
- Nntp-Posting-Host: pdv3.fmr.maschinenbau.th-darmstadt.de
- Organization: TH-Darmstadt
- Lines: 59
-
- In article <1992Aug13.064156.2539@Informatik.TU-Muenchen.DE> roell@informatik.tu-muenchen.de (Thomas Roell) writes:
-
- A) I regard your X11 port as one of the best available for standard
- graphic adaptors in PC world !
-
- > >1) Without a coprocessor, graphic in a PC means bit manipulation by CPU.
- > >This may eat up most of the available bandwidth.
-
- > Yes, but in localbus designs you have the bandwidth available. And if
- > you have a simple framebuffer directly attached to the CPU it is
- > *very* fast.
-
- .... but in no way special suited for bitmanipulation and clipping ...
-
- > >2) As a coprocessor allows to use protocols at a much higher level,
- > >like X or Phigs, communication overhead _shrinks_ tremendously.
- > >This has been proven with PC-graphic adapters running Xserver themselves,
- > >no CPU had to write to video memory anymore.
-
- > Well, then you hit another effect. The CPUs are getting faster faster
- > than the graphics chips do. Like the 34020 is about 6 MIPS, while a
- > 486 is much higher (think around 20 on a 486/50). That means that the
- > main CPU is just waiting for the Graphics board the do something ...
-
- NO! Compare current architectures to current architectures, not
- outdated ones like 34020 [ >>> 20 << ]. BTW: Does not an 34c050 exist
- meanwhile?
-
- > Another performance wall you hit is the communication between adaptor
- > and CPU. Normally they want to have all graphics requests in a special
- > format encoded, which means the 486 is quite busy to translate the
- > users requests. And not to forget you have to go over a bus, which
- > means you have to do busarbitrating (like queue polling).
-
- Common architectures use real double ported memory or fifos to
- interface client [ports] to server [engine]. No need for arbitration.
- There is no special encoding necessary, as X uses a prescribed protocol
- anyway.
-
- >
- > An approch like this will buy you much more than a highpriced special
- > Graphics board. Or why do you think are these RISCy GEs faster under X
- > than the 340x0 based boards ?
- >
-
- First, 34020s are outdated...
- Second, those RISCies outperforming free available graphic processors
- employ their own property one, like
- - GSX board by SUN,
- - graphic engine and clipping pipeline by SGI for SGI-4Dxxx.
-
- Or why do you think sell fast graphic subsystems like sliced bread,
- like those from Raythenon?
-
- best adams
-
-
-
-
-