From owner-freebsd-stable@FreeBSD.ORG Sat May 9 12:07:16 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEB5F106566B; Sat, 9 May 2009 12:07:16 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id AD8828FC17; Sat, 9 May 2009 12:07:16 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from [192.168.1.4] (adsl-154-182-184.bna.bellsouth.net [68.154.182.184]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n49C78Ch002342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 9 May 2009 08:07:08 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland <rnoland@FreeBSD.org> To: Dominic Fandrey <kamikaze@bsdforen.de> In-Reply-To: <4A053E52.5030602@bsdforen.de> References: <1238293386.00093672.1238281804@10.7.7.3> <49CF0803.1070505@FreeBSD.org> <49CF2F8D.6000905@bsdforen.de> <49CF4EB9.60108@FreeBSD.org> <49CF49F5.6010800@bsdforen.de> <49CF615A.6050304@FreeBSD.org> <49CF595A.30805@bsdforen.de> <49CF6B28.2080400@FreeBSD.org> <49CF60AB.4040709@bsdforen.de> <49CF6899.2060002@bsdforen.de> <49CF8E8D.1080604@bsdforen.de> <49CF9C19.3020509@FreeBSD.org> <49D5DA33.4010800@bsdforen.de> <1238778004.65025.30.camel@balrog.2hip.net> <49DF5D60.9010803@bsdforen.de> <1239384104.1922.70.camel@balrog.2hip.net> <4A053E52.5030602@bsdforen.de> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-7lYvHUPjFi8yZb42B3xx" Organization: FreeBSD Date: Sat, 09 May 2009 07:06:46 -0500 Message-Id: <1241870806.1733.61.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1.1 FreeBSD GNOME Team Port X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_SORBS_DUL,RDNS_DYNAMIC autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: Alexander Motin <mav@FreeBSD.org>, freebsd-stable@freebsd.org Subject: Re: powerd broken X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 09 May 2009 12:07:17 -0000 --=-7lYvHUPjFi8yZb42B3xx Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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 com= mit > >>> 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 cas= es. > >>> I *think* the only outstanding issue I have with Intel is if somethin= g > >>> is rendering (synced to vblank or not) when the display goes into dpm= s > >>> 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 probab= ly > >>> isn't a huge issue, but running gears while the display is asleep kee= ps > >>> the cpu at 100%, which isn't ideal. Normal apps that aren't trying t= o > >>> 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. > >=20 > > Things are still not quite right with the Intel driver. But performanc= e > > regressions are reported across Linux as well. A little of this might > > be us, but most of it is Intel... > >=20 >=20 > 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. >=20 > 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? robert. > Thanks a lot. >=20 > Regards --=20 Robert Noland <rnoland@FreeBSD.org> FreeBSD --=-7lYvHUPjFi8yZb42B3xx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEUEABECAAYFAkoFcdYACgkQM4TrQ4qfROPdtgCXaZO9jXX7bQqq4F81LPKgyA+N lACeM0PrzpTeKRsqTm1XGESUbw92Rvo= =7tk2 -----END PGP SIGNATURE----- --=-7lYvHUPjFi8yZb42B3xx--