All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 214425] [drm][amdgpu][TTM] Page pool memory never gets freed
Date: Sat, 15 Oct 2022 16:14:02 +0000	[thread overview]
Message-ID: <bug-214425-2300-r2QxyhUemK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214425-2300@https.bugzilla.kernel.org/>

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

--- Comment #4 from Rafael Ristovski (rafael.ristovski@gmail.com) ---
For what its worth, the following horrible incantation managed to release 2+GB
of TTM buffers on one of my machines, after I purposefully ran a VRAM intensive
game:
> for i in {1..1000}; do cat /sys/kernel/debug/ttm/page_pool_shrink; done

This seems to be the only sysfs mechanism to cause the memory to get released,
and as of now I am not aware of a... better and mainly "cleaner" alternative.

Newer kernel versions seem to feature
https://www.kernel.org/doc/html/next/admin-guide/mm/shrinker_debugfs.html,
which might be a better alternative, but I have not tested it yet, and its
usage is not exactly clear to me.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2022-10-15 16:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 21:09 [Bug 214425] New: [drm][amdgpu][TTM] Page pool memory never gets freed bugzilla-daemon
2022-10-15 14:34 ` [Bug 214425] " bugzilla-daemon
2022-10-15 14:47 ` bugzilla-daemon
2022-10-15 15:05 ` bugzilla-daemon
2022-10-15 16:14 ` bugzilla-daemon [this message]

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=bug-214425-2300-r2QxyhUemK@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=dri-devel@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.