All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Doerffel <tobias.doerffel@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Extreme memory usage when running USDX with Intel driver
Date: Tue, 4 May 2010 01:19:01 +0200	[thread overview]
Message-ID: <201005040119.08034.tobias.doerffel@gmail.com> (raw)


[-- Attachment #1.1: Type: Text/Plain, Size: 2163 bytes --]

Hi,

I have serious problems with running UltraStar Deluxe (a free OpenGL-based
karaoke program) on an Intel graphic card (945GME). When starting the program,
the system starts to use more than 1,5 GB of RAM for (I guess) GEM stuff. I 
can't blame the program as it's running fine with both swrast (on the same 
computer and setup) and the nouveau driver on another computer and itself 
consumes about 100 MB of RAM.

I collected some data describing the system status after the program has been 
started up (and switched to tty0 in order to get these values).

With Mesa 7.9 /proc/dri/0/gem_object tells me

8996 objects
-1422700544 object bytes
3 pinned
19365888 pin bytes
140005376 gtt bytes
260308992 gtt total

With Mesa 7.8.1 it looks like the following:

2655 objects
-1792622592 object bytes
3 pinned
19365888 pin bytes
233402368 gtt bytes
260308992 gtt total

At the same time /proc/<PID>/smaps has about 2500 similiar entries looking 
like

1007e000-1017e000 rw-s 20ac0e000 00:05 314       /dev/dri/card0
Size:               1024 kB
Rss:                   0 kB
Pss:                   0 kB
Shared_Clean:          0 kB
Shared_Dirty:          0 kB
Private_Clean:         0 kB
Private_Dirty:         0 kB
Referenced:            0 kB
Swap:                  0 kB
KernelPageSize:        4 kB
MMUPageSize:           4 kB


/proc/dri/0/gem_names contains

  name     size handles refcount
name 1 size 4194304
     1  4194304       2        5
name 2 size 4194304
     2  4194304       2        4
name 3 size 16777216
     3 16777216       1        4


My setup is the latest kernel with latest commits from the drm-intel-next 
branch. Same for xf86-video-intel and libdrm (both compiled from Git). XServer 
version is 1.8. Mesa as written above. What could I do further to track down 
the problem?

From what I saw in the source code, the program creates lots of textures for
individual glyphs of fonts. The extreme memory usage seems to start while the 
several thousands of textures are being created. I'm just wondering that 
everything works fine with other drivers.

Best regards,

Toby

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2010-05-03 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 23:19 Tobias Doerffel [this message]
2010-05-04  1:24 ` Extreme memory usage when running USDX with Intel driver Eric Anholt
2010-05-04 16:19   ` Eric Anholt
2010-05-04 22:27   ` Tobias Doerffel

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=201005040119.08034.tobias.doerffel@gmail.com \
    --to=tobias.doerffel@gmail.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 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.