From: Eric Anholt Subject: Re: [PATCH] drm/i915: support low power watermarks on Ironlake Date: Thu, 23 Dec 2010 19:11:55 -0800 Message-ID: <87mxnvn9tw.fsf@pollan.anholt.net> References: <20101221131023.2f94306e@jbarnes-desktop> <5b55a1$j23fak@fmsmga002.fm.intel.com> <0d30dc$ki5qgc@orsmga001.jf.intel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1395942739==" Return-path: In-Reply-To: <0d30dc$ki5qgc@orsmga001.jf.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Chris Wilson , Jesse Barnes , intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org --===============1395942739== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" --=-=-= Content-Transfer-Encoding: quoted-printable On Thu, 23 Dec 2010 12:30:29 +0000, Chris Wilson = wrote: > On Thu, 23 Dec 2010 12:07:22 +0000, Chris Wilson wrote: > > I tweaked the patch to pass the watermark structs through to the check > > routine. The box survives s2ram, but I have now also experienced the > > mysterious slow down after resuming. >=20 > As Eric first said the cause for the slow down is that writing through the > GTT becomes very slow: >=20 > Before suspending: > Time to pwrite 16k through the CPU: 0.000004s > Time to read 16k through a GTT map: 0.000901s > Time to write 16k through a GTT map: 0.000023s > Time to read 16k (again) through a GTT map: 0.000900s > Time to pwrite 16k through the GTT: 0.000007s >=20 > After resume: > Time to pwrite 16k through the CPU: 0.000004s > Time to read 16k through a GTT map: 0.000900s > Time to write 16k through a GTT map: 0.000876s > Time to read 16k (again) through a GTT map: 0.000899s > Time to pwrite 16k through the GTT: 0.000431s >=20 > The implication being that our mapping goes from write-combining to > uncached? > -Chris I found that the results were not just "slow like no write combining", but timing-dependent, too. Repeated runs of a timing app would get fast sometimes, slow other times, and sometimes the switch from fast->slow or slow->fast would happen in the middle of a run. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk0UD3sACgkQHUdvYGzw6veSjwCePpu25Vv+nm5ZdJBYaXyoIjYM JUoAoJnQeelYxqn0p+T159+/1yhXBT7Y =w9tl -----END PGP SIGNATURE----- --=-=-=-- --===============1395942739== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============1395942739==--