From: Chris Wilson <chris@chris-wilson.co.uk>
To: Peter Clifton <pcjc2@cam.ac.uk>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: i915_gem_evict_something in sysprof trace using VBOs
Date: Fri, 05 Nov 2010 10:35:55 +0000 [thread overview]
Message-ID: <5b55a1$iitkru@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1288952467.24411.44.camel@pcjc2lap>
On Fri, 05 Nov 2010 10:21:07 +0000, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> I was playing with my VBO code, and noticed this sysprof trace
> (non-interesting stuff pruned):
>
> drm_ioctl 0.13% 56.08%
> i915_gem_execbuffer2 0.00% 32.50%
> i915_gem_do_execbuffer 0.08% 32.50%
> i915_gem_object_pin 0.00% 17.47%
> i915_gem_object_bind_to_gtt 0.03% 17.44%
> i915_gem_evict_something 0.00% 15.54%
> i915_gem_object_unbind 0.00% 15.31%
> i915_gem_object_set_to_cpu_domain 0.00% 13.33%
> i915_gem_clflush_object 0.00% 13.33%
> i915_gem_clflush_object 0.00% 14.29%
> i915_gem_mmap_gtt_ioctl 0.00% 10.74%
> i915_gem_set_domain_ioctl 0.00% 4.98%
>
>
> The i915_gem_evict_something has me curious. Presumably I have too many
> pages of data actively being used by the GPU (or mapped).
Yes, you are suffering from aperture thrashing. There are a few ways to
workaround this (1) decrease the size of your working set (reduce texture
sizes, reuse as many buffers within the aperture as possible), (2)
increase the size of the aperture (check your BIOS AGP size and apply
drm-intel-next to get the benefit of the full-GTT), (3) add an uncached
page cache to avoid those costly clflushes.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-11-05 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 10:21 i915_gem_evict_something in sysprof trace using VBOs Peter Clifton
2010-11-05 10:35 ` Chris Wilson [this message]
2010-11-05 11:44 ` Peter Clifton
2010-11-05 14:30 ` Peter Clifton
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='5b55a1$iitkru@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pcjc2@cam.ac.uk \
/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