From: "Danilo Krummrich" <dakr@kernel.org>
To: "Dave Airlie" <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
"Dave Airlie" <airlied@redhat.com>,
"Christian Koenig" <christian.koenig@amd.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Simona Vetter" <simona.vetter@ffwll.ch>,
dri-devel <dri-devel-bounces@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] ttm/bo: add an API to populate a bo before exporting.
Date: Tue, 09 Sep 2025 09:31:46 +0200 [thread overview]
Message-ID: <DCO3EPQXQSUL.2XUR07VDP2Q38@kernel.org> (raw)
In-Reply-To: <20250904021643.2050497-1-airlied@gmail.com>
On Thu Sep 4, 2025 at 4:16 AM CEST, Dave Airlie wrote:
> From: Dave Airlie <airlied@redhat.com>
>
> While discussing cgroups we noticed a problem where you could export
> a BO to a dma-buf without having it ever being backed or accounted for.
>
> This meant in low memory situations or eventually with cgroups, a
> lower privledged process might cause the compositor to try and allocate
> a lot of memory on it's behalf and this could fail. At least make
> sure the exporter has managed to allocate the RAM at least once
> before exporting the object.
The below use of TTM_PL_FLAG_MEMCG suggests that this goes on top of your cgroup
patch series. However, wouldn't a similar change make sense regardless?
next prev parent reply other threads:[~2025-09-09 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 2:16 [PATCH 1/4] ttm/bo: add an API to populate a bo before exporting Dave Airlie
2025-09-04 2:16 ` [PATCH 2/4] amdgpu: populate buffers before exporting them Dave Airlie
2025-09-04 2:16 ` [PATCH 3/4] nouveau: " Dave Airlie
2025-09-09 7:33 ` Danilo Krummrich
2025-09-04 2:16 ` [PATCH 4/4] xe: " Dave Airlie
2025-09-04 7:26 ` Thomas Hellström
2025-09-04 7:20 ` [PATCH 1/4] ttm/bo: add an API to populate a bo before exporting Thomas Hellström
2025-09-04 11:13 ` Christian König
2025-09-09 7:31 ` Danilo Krummrich [this message]
2025-09-09 7:39 ` David Airlie
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=DCO3EPQXQSUL.2XUR07VDP2Q38@kernel.org \
--to=dakr@kernel.org \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel-bounces@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=simona.vetter@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
/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.