All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Clifton <pcjc2@cam.ac.uk>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: i915_gem_evict_something in sysprof trace using VBOs
Date: Fri, 05 Nov 2010 10:21:07 +0000	[thread overview]
Message-ID: <1288952467.24411.44.camel@pcjc2lap> (raw)

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).

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)

             reply	other threads:[~2010-11-05 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 10:21 Peter Clifton [this message]
2010-11-05 10:35 ` i915_gem_evict_something in sysprof trace using VBOs Chris Wilson
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=1288952467.24411.44.camel@pcjc2lap \
    --to=pcjc2@cam.ac.uk \
    --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 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.