public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 4/5] drm/i915: Use eLLC/LLC by default when available
Date: Thu, 4 Jul 2013 11:40:37 -0700	[thread overview]
Message-ID: <20130704184036.GJ5488@bwidawsk.net> (raw)
In-Reply-To: <20130704181709.GH18285@phenom.ffwll.local>

On Thu, Jul 04, 2013 at 08:17:09PM +0200, Daniel Vetter wrote:
> On Thu, Jul 04, 2013 at 11:02:06AM -0700, Ben Widawsky wrote:
> > DRI clients really should be using MOCS to get fine grained streaming
> > cache controls. With that note, I *hope* that this patch doesn't improve
> > performance overwhelmingly, because if it does - it means there is a
> > problem elsewhere.
> > 
> > In any case, the kernel, and old userspace should get some benefit from
> > this, so let's do it. eLLC is always a good default, and really not
> > using it is the special case for MOCS.
> > 
> > References: http://www.intel.com/newsroom/kits/restricted/ha$well!/pdfs/4th_Gen_Intel_Core_PressBriefing_5-29.pdf (page 57)
> > 
> > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> 
> Iris is the marketing name and likely to stick around for a bit (like HD
> Graphics), I'd vote to use the codename for this thing here, i.e. crw.
> -Daniel
>
I think we've agreed on IRC to leave this as is?
-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2013-07-04 18:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 18:02 [PATCH 1/5] drm/i915/hsw: Set correct Haswell PTE encodings Ben Widawsky
2013-07-04 18:02 ` [PATCH 2/5] drm/i915: Define some of the eLLC magic Ben Widawsky
2013-07-13  0:02   ` Rodrigo Vivi
2013-07-14 20:36     ` Ben Widawsky
2013-07-04 18:02 ` [PATCH 3/5] drm/i915: store eLLC size Ben Widawsky
2013-07-04 18:42   ` [PATCH 3.5/5] drm/i915: Do eLLC detection earlier Ben Widawsky
2013-07-13  0:04     ` Rodrigo Vivi
2013-07-13  9:39     ` Daniel Vetter
2013-07-14 20:37       ` Ben Widawsky
2013-07-16  6:02   ` [PATCH 3/5] drm/i915: store eLLC size Daniel Vetter
2013-07-04 18:02 ` [PATCH 4/5] drm/i915: Use eLLC/LLC by default when available Ben Widawsky
2013-07-04 18:17   ` Daniel Vetter
2013-07-04 18:40     ` Ben Widawsky [this message]
2013-07-13  0:08       ` Rodrigo Vivi
2013-07-04 18:02 ` [PATCH 5/5] drm/i915: debugfs entries for [e]LLC Ben Widawsky
2013-07-04 18:14   ` Daniel Vetter
2013-07-04 18:40     ` Ben Widawsky
2013-07-04 18:43       ` Daniel Vetter
2013-07-04 18:46         ` Ben Widawsky
2013-07-09 18:35           ` Chad Versace
2013-07-09 20:16             ` Ben Widawsky
2013-07-04 18:47   ` [PATCH 6/6] drm/i915: Add a param for eLLC size Ben Widawsky
2013-07-16  6:10     ` Daniel Vetter
2013-07-13  0:11   ` [PATCH 5/5] drm/i915: debugfs entries for [e]LLC Rodrigo Vivi
2013-07-13  0:00 ` [PATCH 1/5] drm/i915/hsw: Set correct Haswell PTE encodings Rodrigo Vivi
2013-07-14 20:34   ` Ben Widawsky
2013-07-15 14:16 ` Damien Lespiau
2013-07-15 14:23 ` Damien Lespiau
2013-07-15 16:54   ` Ben Widawsky
2013-07-16  6:00     ` Daniel Vetter

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=20130704184036.GJ5488@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=daniel@ffwll.ch \
    --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