All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 31412] radeon memory leak
Date: Sun, 20 Mar 2011 20:40:08 GMT	[thread overview]
Message-ID: <201103202040.p2KKe8eS022615@demeter2.kernel.org> (raw)
In-Reply-To: <bug-31412-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=31412





--- Comment #10 from Kevin <kjslag@gmail.com>  2011-03-20 20:40:04 ---
echo 3 > /proc/sys/vm/drop_caches
cleared all of the memory. Thank you! See output below (ran after exiting X).
I didn't try unloading the gpu stack. I can try it if you like.


I also saved /proc/slabinfo before and after I dropped the caches. If I'm
interpreting the file correctly, I only notice large drops in ext4 filesystem
stuff. Is there a way to tell which slabs are considered buffers or cache?


# free -m
             total       used       free     shared    buffers     cached
Mem:          5920       4318       1602          0        113       2465
-/+ buffers/cache:       1740       4180
Swap:         7998          0       7998
# echo 3 > /proc/sys/vm/drop_caches
# free -m
             total       used       free     shared    buffers     cached
Mem:          5920        225       5695          0          3         12
-/+ buffers/cache:        209       5711
Swap:         7998          0       7998

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

  parent reply	other threads:[~2011-03-20 20:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-31412-2300@https.bugzilla.kernel.org/>
2011-03-18 20:30 ` [Bug 31412] radeon memory leak bugzilla-daemon
2011-03-18 20:31 ` bugzilla-daemon
2011-03-18 20:47 ` bugzilla-daemon
2011-03-18 21:01 ` bugzilla-daemon
2011-03-18 21:25 ` bugzilla-daemon
2011-03-19  7:16 ` bugzilla-daemon
2011-03-19  7:17 ` bugzilla-daemon
2011-03-19  9:15 ` bugzilla-daemon
2011-03-19  9:17 ` bugzilla-daemon
2011-03-19 22:07 ` bugzilla-daemon
2011-03-20 20:40 ` bugzilla-daemon [this message]
2011-03-20 20:40 ` bugzilla-daemon
2011-03-20 20:40 ` bugzilla-daemon
2011-06-02  2:57 ` bugzilla-daemon
2011-06-02  5:56 ` bugzilla-daemon
2011-06-02 17:24 ` bugzilla-daemon

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=201103202040.p2KKe8eS022615@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.