From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: set cache sharing policy to max sharing on SNB+
Date: Sat, 02 Jul 2011 11:47:50 +0100 [thread overview]
Message-ID: <aefc95$ljcg9@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1309563307-5480-1-git-send-email-jbarnes@virtuousgeek.org>
On Fri, 1 Jul 2011 16:35:07 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> By default, the GPU will only share a very small portion of the CPU
> cache. With this change, both the GPU and CPU will have full access to
> the cache, which should help (sometimes a lot) in most cases.
Joy, this looks to be at best a mixed blessing. For CPU bound games like
padman, it degrades performance by about 5% on my desktop SNB. But for
nexuiz, there appears to be little change. The ddx shows further regression
of the order of 10%. The immediate suspect is that it hurts the use of
pixman for trapezoid mask generation, which whilst being less than ideal
behaviour and will be fixed in the near future, is indicative of the sort
of negative impact this change will have on CPU-memory bound applications.
Conversely the equivalent spans-based code is about the only example I
found that is sped up by the patch, by about 3%.
Having just checked up on 0x900c, I'm even more confused. From my old
specs, the register is SNPCR, the snoop control register, which makes
more sense than MBC, and that 0<<21 is for the maximum uncore resources,
the default setting and the default on my SNB, with 1<<21 being the
medium setting. Now, the only reference I have is the register dump with
no explanation of what the resource that is actually being controlled...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2011-07-02 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 23:35 [PATCH] drm/i915: set cache sharing policy to max sharing on SNB+ Jesse Barnes
2011-07-02 7:20 ` Chris Wilson
2011-07-02 10:47 ` Chris Wilson [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='aefc95$ljcg9@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.