From: Chris Wilson Subject: Re: [PATCH] drm/i915: support low power watermarks on Ironlake Date: Thu, 23 Dec 2010 12:30:29 +0000 Message-ID: <0d30dc$ki5qgc@orsmga001.jf.intel.com> References: <20101221131023.2f94306e@jbarnes-desktop> <5b55a1$j23fak@fmsmga002.fm.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by gabe.freedesktop.org (Postfix) with ESMTP id 6DB2B9EBA2 for ; Thu, 23 Dec 2010 04:34:10 -0800 (PST) In-Reply-To: <5b55a1$j23fak@fmsmga002.fm.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: Jesse Barnes , intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org 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. As Eric first said the cause for the slow down is that writing through the GTT becomes very slow: 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 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 The implication being that our mapping goes from write-combining to uncached? -Chris -- Chris Wilson, Intel Open Source Technology Centre