On Sat, 2009-05-09 at 15:10 +0200, Dominic Fandrey wrote: > Robert Noland wrote: > > On Sat, 2009-05-09 at 10:26 +0200, Dominic Fandrey wrote: > >> Robert Noland wrote: > >>> On Fri, 2009-04-10 at 16:53 +0200, Dominic Fandrey wrote: > >>>> Robert Noland wrote: > >>>>> I've been working on the Intel vblank / irq issues. Every time I commit > >>>>> something thinking that I have it resolved, it isn't. So I'm waiting on > >>>>> hardware to arrive that will let me test this all more thoroughly. I do > >>>>> have a patch that I think fixes most of the issues on Intel, but the ddx > >>>>> driver is still doing some silly things that cause issues in some cases. > >>>>> I *think* the only outstanding issue I have with Intel is if something > >>>>> is rendering (synced to vblank or not) when the display goes into dpms > >>>>> sleep, there isn't anything to block that app, so it renders as hard as > >>>>> it can even though it isn't being displayed. In reality, this probably > >>>>> isn't a huge issue, but running gears while the display is asleep keeps > >>>>> the cpu at 100%, which isn't ideal. Normal apps that aren't trying to > >>>>> draw as fast as they can, shouldn't cause an issue. > >>>> With the latest drm, the IRQ craziness is gone. However, the crappy > >>>> performance remains. 2 months ago a RELENG_7 with all packages > >>>> up to date yielded 124fps in a q3 timedemo that now yields 80fps. > >>> Things are still not quite right with the Intel driver. But performance > >>> regressions are reported across Linux as well. A little of this might > >>> be us, but most of it is Intel... > >>> > >> I don't know what you did with the last update, but performance is now > >> better than ever (2% above what it used to be), which equels 3-4 more > >> frames in ioQuake3 or 200 more in glxgears. > >> > >> The uptime of the notebook is now 15 hours and the interrupt load > >> insignificant. I get no more than 8000 interrupts per seconds. > >> 4000 of these are CPU timers (2000 for each core) and 1000 more are > >> from my mouse, when I move it very fast. Around 2500 from vgapci, when > >> I run glxgears and the rest is just scraps of whatever else is running > >> (e.g. sound). > > > > Which update, what? I haven't touched the kernel tree in a while, just > > trying to sort it all out with patches here and there. Are you saying > > the the 2.7.0 intel driver helped? Or maybe the Xserver or mesa > > updates? > > I update my ports daily, without really looking at what. I think > xorg-server was one of them. It must have been something that happened > during the last 48 hours.
Ok, well server, mesa and intel driver all got updates in my sweep the other day. robert. > > robert. > > > >> Thanks a lot. > >> > >> Regards > -- Robert Noland <[email protected]> FreeBSD
signature.asc
Description: This is a digitally signed message part
