Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Eric Anholt <eric@anholt.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Prefer setting PTE cache age to 3
Date: Mon, 25 Nov 2013 09:50:49 +0100	[thread overview]
Message-ID: <20131125085049.GV27344@phenom.ffwll.local> (raw)
In-Reply-To: <87wqk0gu32.fsf@eliezer.anholt.net>

On Fri, Nov 22, 2013 at 10:38:41AM -0800, Eric Anholt wrote:
> Chris Wilson <chris@chris-wilson.co.uk> writes:
> 
> > We have conflicting benchmark data that suggest either age 0 or age 3 is
> > better. However, the earlier benchmark on which we based the switch to
> > age 0
> >
> > (commit 0d8ff15e9a15f2b393e53337a107b7a1e5919b6d
> > Author: Ben Widawsky <benjamin.widawsky@intel.com>
> > Date:   Thu Jul 4 11:02:03 2013 -0700
> >
> >     drm/i915/hsw: Set correct Haswell PTE encodings)
> >
> > actually seems to prefer the default PTE encoding as age 3. Presumably,
> > this is in part due to the use of MOCS to override the PTE encodings
> > when appropriate.
> 
> This bothered me when reviewing the kernel code for hsw.  Thanks.
> 
> Reviewed-by: Eric Anholt <eric@anholt.net>
> 
> Note that userspace doesn't currently set MOCS other than the L3 bit.
> I'm hoping we end up not having to, since we don't have a WT option in
> MOCS other than "just listen to the PTEs".

Picked up for -fixes, thanks for the patch&review.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2013-11-25  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 10:37 [PATCH] drm/i915: Prefer setting PTE cache age to 3 Chris Wilson
2013-11-22 17:53 ` Jesse Barnes
2013-11-22 18:26   ` Ville Syrjälä
2013-11-22 18:38 ` Eric Anholt
2013-11-25  8:50   ` Daniel Vetter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131125085049.GV27344@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=eric@anholt.net \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox