From: Chris Wilson <chris@chris-wilson.co.uk>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Use I915_MAX_PIPES instead of hardcoded value
Date: Wed, 20 Feb 2013 15:07:10 +0000 [thread overview]
Message-ID: <20130220150710.GB613@cantiga.alporthouse.com> (raw)
In-Reply-To: <1361371636-6152-1-git-send-email-ville.syrjala@linux.intel.com>
On Wed, Feb 20, 2013 at 04:47:16PM +0200, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> The pipestat array size should have space for every pipe in the system.
> Use the define we have for it.
Tbh, I think that cache should die. I think the hitrate is near zero,
and offers no benefit over just writing the register directly.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-02-20 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 14:47 [PATCH] drm/i915: Use I915_MAX_PIPES instead of hardcoded value ville.syrjala
2013-02-20 15:07 ` Chris Wilson [this message]
2013-02-20 18:14 ` Jesse Barnes
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=20130220150710.GB613@cantiga.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/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