<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Chris,<o:p></o:p> If using “x11perf –rgbftext” test, it will give lx_check_composite a call with pSrc(ARGB) and pDst(ARGB) that we can’t handle.<o:p></o:p> So I think this part acceleration is not possible in our driver. Right now, with my patch, we can accelerate with “-aa10text” and “aa24text”. We accelerate the PictOpAdd with pSrc(A8) and pDst(A8).<o:p></o:p> If you care only the “-rgbftext”, we have no way now; otherwise, you can use my patch to give a glyph performance advanced.<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> Frank<o:p></o:p> <o:p> </o:p> <div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: Christophe Lindheimer [mailto:christophe.lindheimer@gmail.com] Sent: 2010年7月26日 21:51 To: <st1:PersonName w:st="on">Mart Raudsepp</st1:PersonName> Cc: Huang, FrankR; xorg-driver-geode@lists.x.org Subject: Re: [Xorg-driver-geode] Driver Perf LX800<o:p></o:p> </div> <o:p> </o:p> <div> <blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt; margin-left:4.8pt;margin-right:0in'> <div> On E, 2010-07-26 at 14:31 +0200, Christophe Lindheimer wrote: > Hi. ><o:p></o:p> </div> <div> > My prob is just that I had much better perfomances with my old > system... ><o:p></o:p> </div> Yes, and what are your typical use cases. What programs and operations are slow. Just the desktop environment in general, I assume.<o:p></o:p> </blockquote> <div> Hard to say.<o:p></o:p> </div> <div> The issue I see is on a big soft running in full screen on a simple X Server.<o:p></o:p> </div> <div> As I have a lot of text on the screen, I chose to test the -rgbftext <o:p></o:p> </div> <div> But my knowledge on X is rather limited...<o:p></o:p> </div> <div>  <o:p></o:p> </div> <blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt; margin-left:4.8pt;margin-right:0in'> <div> > > I run a x11perf -rgbftext. >  Old config :81300 / s >  New config : 36000 / s<o:p></o:p> </div> Are you sure -rgbftext measures what is important? I guess it measures no anti-aliasing text drawing, not sure how we fare there with the optimized code (that isn't in 2.11.8 or even GIT yet). Is your desktop really configured to no anti-aliasing at all? We typically benchmark the common case with x11perf -aa10text and x11perf -aa24text for anti-aliased text In the future it will be important for speed to not use subpixel smoothing (the anti-aliasing style, that takes advandance of the fact that LCD screens are made of red, green and blue subpixels), as that we won't be able to accelerate anytime soon (if ever).<o:p></o:p> <div> > But I guess (and hope) that Mart's analysis is OK and that the > performances will get much better once the driver will be fully > optimized...<o:p></o:p> </div> Meanwhile you can force most things to software with the option Option "MigrationHeuristic" "greedy" in your xorg.conf or xorg.conf.d/ (with xserver-1.8+ if migrated to that use already). That should give a bit better results until you are able to have more optimized driver. There are patches on the mailing list for making text go 5-10 times faster though. After those patches are finalized, we'll of course have work ahead on optimizing various other rendering of the desktop besides text drawing. Regards, <st1:PersonName w:st="on">Mart Raudsepp</st1:PersonName><o:p></o:p> </blockquote> </div> <o:p> </o:p> </div> </div> </body> </html>