From: Ben Widawsky <benjamin.widawsky@intel.com>
To: Intel GFX <intel-gfx@lists.freedesktop.org>
Cc: Ben Widawsky <benjamin.widawsky@intel.com>
Subject: [PATCH 0/6] Prefer wbinvd() where appropriate
Date: Mon, 9 Feb 2015 13:54:13 -0800 [thread overview]
Message-ID: <1423518859-6199-1-git-send-email-benjamin.widawsky@intel.com> (raw)
A while back we had a workload which severely suffered from excessive
clflushing. I sent out a patch series which solved this generically in DRM core,
but that had the unfortunate side effect of possibly regressing non-intel
platforms.
I've re-spun the series to only take this shortcut when on an Intel platform.
This series is untested by me since we've now worked around the problem in a
different way within mesa. Jesse asked me to send this out, though I don't have
time to see if it's still useful (until my mesa patches are merged, it would be
useful, but afterwards, I do not know). I also didn't check that I rebased
things properly.
Do what you want with them...
Ben Widawsky (6):
drm/i915: Remove the useless flush_chipset
drm/i915: Pass eb_vmas to execbuffer implementations
drm/i915: Opportunistically reduce flushing at execbuf
drm/i915: Add debugfs knobs for wbinvd threshold
drm/i915: Extract checking the necessity of flush
drm/i915: obey wbinvd threshold in more places
drivers/gpu/drm/i915/i915_debugfs.c | 34 +++++++++++
drivers/gpu/drm/i915/i915_drv.h | 25 +++++++-
drivers/gpu/drm/i915/i915_gem.c | 96 ++++++++++++++++++++----------
drivers/gpu/drm/i915/i915_gem_execbuffer.c | 46 +++++++-------
drivers/gpu/drm/i915/i915_gem_gtt.c | 13 +++-
drivers/gpu/drm/i915/intel_lrc.c | 21 ++++---
drivers/gpu/drm/i915/intel_lrc.h | 3 +-
7 files changed, 172 insertions(+), 66 deletions(-)
--
2.3.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-02-09 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 21:54 Ben Widawsky [this message]
2015-02-09 21:54 ` [PATCH 1/6] drm/i915: Remove the useless flush_chipset Ben Widawsky
2015-02-10 9:18 ` Chris Wilson
2015-02-09 21:54 ` [PATCH 2/6] drm/i915: Pass eb_vmas to execbuffer implementations Ben Widawsky
2015-02-10 9:19 ` Chris Wilson
2015-02-09 21:54 ` [PATCH 3/6] drm/i915: Opportunistically reduce flushing at execbuf Ben Widawsky
2015-02-10 9:21 ` Chris Wilson
2015-02-09 21:54 ` [PATCH 4/6] drm/i915: Add debugfs knobs for wbinvd threshold Ben Widawsky
2015-02-09 21:54 ` [PATCH 5/6] drm/i915: Extract checking the necessity of flush Ben Widawsky
2015-02-09 21:54 ` [PATCH 6/6] drm/i915: obey wbinvd threshold in more places Ben Widawsky
2015-02-10 9:28 ` Chris Wilson
2015-02-10 20:49 ` shuang.he
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=1423518859-6199-1-git-send-email-benjamin.widawsky@intel.com \
--to=benjamin.widawsky@intel.com \
--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