From: "Christian König" <christian.koenig@amd.com>
To: "T.J. Mercier" <tjmercier@google.com>,
Eric Chanudet <echanude@redhat.com>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Brian Starkey <Brian.Starkey@arm.com>,
John Stultz <jstultz@google.com>,
Maxime Ripard <mripard@redhat.com>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dma-buf: heaps: add parameter to account allocations using cgroup
Date: Mon, 19 Jan 2026 10:49:48 +0100 [thread overview]
Message-ID: <c3d66415-0e2e-4945-917f-4c47f16bf743@amd.com> (raw)
In-Reply-To: <CABdmKX1ZCkF2N1Esi6Uo=jK=soXZe_eWhSSxHtMTcRWs-ZUYog@mail.gmail.com>
On 1/16/26 23:36, T.J. Mercier wrote:
> On Fri, Jan 16, 2026 at 12:06 PM Eric Chanudet <echanude@redhat.com> wrote:
>>
>> Add a parameter to enable dma-buf heaps allocation accounting using
>> cgroup for heaps that implement it. It is disabled by default as doing
>> so incurs caveats based on how memcg currently accounts for shared
>> buffers.
>>
>> Signed-off-by: Eric Chanudet <echanude@redhat.com>
>
> Reviewed-by: T.J. Mercier <tjmercier@google.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Should I push that into drm-misc-next or does anybody else has commit access?
Regards,
Christian.
next prev parent reply other threads:[~2026-01-19 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 20:05 [PATCH v3 0/2] dma-buf: system_heap: account for system heap allocation in memcg Eric Chanudet
2026-01-16 20:05 ` [PATCH v3 1/2] dma-buf: heaps: add parameter to account allocations using cgroup Eric Chanudet
2026-01-16 22:36 ` T.J. Mercier
2026-01-19 9:49 ` Christian König [this message]
2026-01-19 13:10 ` Sumit Semwal
2026-01-16 20:05 ` [PATCH v3 2/2] dma-buf: system_heap: account for system heap allocation in memcg Eric Chanudet
2026-01-16 22:36 ` T.J. Mercier
2026-01-19 13:09 ` Sumit Semwal
2026-01-19 13:33 ` [PATCH v3 0/2] " Maxime Ripard
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=c3d66415-0e2e-4945-917f-4c47f16bf743@amd.com \
--to=christian.koenig@amd.com \
--cc=Brian.Starkey@arm.com \
--cc=benjamin.gaignard@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=echanude@redhat.com \
--cc=jstultz@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mripard@redhat.com \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®