From: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: "T.J. Mercier" <tjmercier-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: daniel-/w4YWyX8dFk@public.gmane.org,
tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
"Maarten Lankhorst"
<maarten.lankhorst-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
"Maxime Ripard" <mripard-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Thomas Zimmermann" <tzimmermann-l3A5Bk7waGM@public.gmane.org>,
"David Airlie" <airlied-cv59FeDIM0c@public.gmane.org>,
"Jonathan Corbet" <corbet-T1hC0tSOHrs@public.gmane.org>,
"Arve Hjønnevåg" <arve-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
"Todd Kjos" <tkjos-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
"Martijn Coenen" <maco-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
"Joel Fernandes"
<joel-QYYGw3jwrUn5owFQY34kdNi2O/JbrIOy@public.gmane.org>,
"Christian Brauner"
<brauner-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Hridya Valsaraju"
<hridya-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
"Suren Baghdasaryan"
<surenb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
"Sumit Semwal"
<sumit.semwal-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"Christian König" <christian.koenig-5C7GfCeVMHo@public.gmane.org>,
"Benjamin Gaignard"
<benjamin.gaignard-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>,
"Liam Mark" <lmark-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
"Laura Abbott" <labbott-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [RFC v5 0/6] Proposal for a GPU cgroup controller
Date: Fri, 22 Apr 2022 16:53:00 +0200 [thread overview]
Message-ID: <YmLBTBd+5RHzr9MK@kroah.com> (raw)
In-Reply-To: <20220420235228.2767816-1-tjmercier-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
On Wed, Apr 20, 2022 at 11:52:18PM +0000, T.J. Mercier wrote:
> This patch series revisits the proposal for a GPU cgroup controller to
> track and limit memory allocations by various device/allocator
> subsystems. The patch series also contains a simple prototype to
> illustrate how Android intends to implement DMA-BUF allocator
> attribution using the GPU cgroup controller. The prototype does not
> include resource limit enforcements.
>
> Changelog:
> v5:
> Rebase on top of v5.18-rc3
Why is a "RFC" series on v5? I treat "RFC" as "not ready to be merged,
if people are interested, please look at it". But v5 seems like you
think this is real.
confused,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "T.J. Mercier" <tjmercier@google.com>
Cc: daniel@ffwll.ch, tj@kernel.org,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@linux.ie>,
"Jonathan Corbet" <corbet@lwn.net>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <brauner@kernel.org>,
"Hridya Valsaraju" <hridya@google.com>,
"Suren Baghdasaryan" <surenb@google.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Benjamin Gaignard" <benjamin.gaignard@collabora.com>,
"Liam Mark" <lmark@codeaurora.org>,
"Laura Abbott" <labbott@redhat.com>,
"Brian Starkey" <Brian.Starkey@arm.com>,
"John Stultz" <john.stultz@linaro.org>,
"Zefan Li" <lizefan.x@bytedance.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Shuah Khan" <shuah@kernel.org>,
jstultz@google.com, cmllamas@google.com, kaleshsingh@google.com,
Kenny.Ho@amd.com, mkoutny@suse.com, skhan@linuxfoundation.org,
kernel-team@android.com, dri-devel@lists.freedesktop.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
cgroups@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [RFC v5 0/6] Proposal for a GPU cgroup controller
Date: Fri, 22 Apr 2022 16:53:00 +0200 [thread overview]
Message-ID: <YmLBTBd+5RHzr9MK@kroah.com> (raw)
In-Reply-To: <20220420235228.2767816-1-tjmercier@google.com>
On Wed, Apr 20, 2022 at 11:52:18PM +0000, T.J. Mercier wrote:
> This patch series revisits the proposal for a GPU cgroup controller to
> track and limit memory allocations by various device/allocator
> subsystems. The patch series also contains a simple prototype to
> illustrate how Android intends to implement DMA-BUF allocator
> attribution using the GPU cgroup controller. The prototype does not
> include resource limit enforcements.
>
> Changelog:
> v5:
> Rebase on top of v5.18-rc3
Why is a "RFC" series on v5? I treat "RFC" as "not ready to be merged,
if people are interested, please look at it". But v5 seems like you
think this is real.
confused,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "T.J. Mercier" <tjmercier@google.com>
Cc: linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
"David Airlie" <airlied@linux.ie>,
cmllamas@google.com, dri-devel@lists.freedesktop.org,
jstultz@google.com, "Zefan Li" <lizefan.x@bytedance.com>,
kaleshsingh@google.com, "Joel Fernandes" <joel@joelfernandes.org>,
"Shuah Khan" <shuah@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Benjamin Gaignard" <benjamin.gaignard@collabora.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Martijn Coenen" <maco@android.com>,
"Laura Abbott" <labbott@redhat.com>,
kernel-team@android.com, linux-media@vger.kernel.org,
"Todd Kjos" <tkjos@android.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
linaro-mm-sig@lists.linaro.org,
"Hridya Valsaraju" <hridya@google.com>,
skhan@linuxfoundation.org, cgroups@vger.kernel.org,
"Suren Baghdasaryan" <surenb@google.com>,
"Christian Brauner" <brauner@kernel.org>,
Kenny.Ho@amd.com, linux-kernel@vger.kernel.org,
"Liam Mark" <lmark@codeaurora.org>,
"Arve Hjønnevåg" <arve@android.com>,
mkoutny@suse.com, "Johannes Weiner" <hannes@cmpxchg.org>,
tj@kernel.org, "Christian König" <christian.koenig@amd.com>
Subject: Re: [RFC v5 0/6] Proposal for a GPU cgroup controller
Date: Fri, 22 Apr 2022 16:53:00 +0200 [thread overview]
Message-ID: <YmLBTBd+5RHzr9MK@kroah.com> (raw)
In-Reply-To: <20220420235228.2767816-1-tjmercier@google.com>
On Wed, Apr 20, 2022 at 11:52:18PM +0000, T.J. Mercier wrote:
> This patch series revisits the proposal for a GPU cgroup controller to
> track and limit memory allocations by various device/allocator
> subsystems. The patch series also contains a simple prototype to
> illustrate how Android intends to implement DMA-BUF allocator
> attribution using the GPU cgroup controller. The prototype does not
> include resource limit enforcements.
>
> Changelog:
> v5:
> Rebase on top of v5.18-rc3
Why is a "RFC" series on v5? I treat "RFC" as "not ready to be merged,
if people are interested, please look at it". But v5 seems like you
think this is real.
confused,
greg k-h
next prev parent reply other threads:[~2022-04-22 14:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 23:52 [RFC v5 0/6] Proposal for a GPU cgroup controller T.J. Mercier
2022-04-20 23:52 ` T.J. Mercier
2022-04-20 23:52 ` T.J. Mercier
2022-04-20 23:52 ` [RFC v5 1/6] gpu: rfc: " T.J. Mercier
2022-04-20 23:52 ` T.J. Mercier
2022-04-21 20:34 ` Tejun Heo
2022-04-21 20:34 ` Tejun Heo
2022-04-21 22:25 ` T.J. Mercier
2022-04-21 22:25 ` T.J. Mercier
2022-04-20 23:52 ` [RFC v5 3/6] dmabuf: heaps: export system_heap buffers with GPU cgroup charging T.J. Mercier
2022-04-20 23:52 ` T.J. Mercier
2022-04-20 23:52 ` [RFC v5 5/6] binder: Add flags to relinquish ownership of fds T.J. Mercier
2022-04-20 23:52 ` T.J. Mercier
2022-04-21 18:28 ` Carlos Llamas
2022-04-21 18:28 ` Carlos Llamas
2022-04-21 22:09 ` T.J. Mercier
2022-04-21 22:09 ` T.J. Mercier
2022-04-20 23:52 ` [RFC v5 6/6] selftests: Add binder cgroup gpu memory transfer tests T.J. Mercier
[not found] ` <20220420235228.2767816-1-tjmercier-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2022-04-20 23:52 ` [RFC v5 2/6] cgroup: gpu: Add a cgroup controller for allocator attribution of GPU memory T.J. Mercier
2022-04-20 23:52 ` T.J. Mercier
2022-04-20 23:52 ` [RFC v5 4/6] dmabuf: Add gpu cgroup charge transfer function T.J. Mercier
2022-04-20 23:52 ` T.J. Mercier
2022-04-20 23:52 ` T.J. Mercier
2022-04-22 14:53 ` Greg Kroah-Hartman [this message]
2022-04-22 14:53 ` [RFC v5 0/6] Proposal for a GPU cgroup controller Greg Kroah-Hartman
2022-04-22 14:53 ` Greg Kroah-Hartman
2022-04-22 16:40 ` T.J. Mercier
2022-04-22 16:40 ` T.J. Mercier
2022-04-22 16:40 ` T.J. Mercier
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=YmLBTBd+5RHzr9MK@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
--cc=airlied-cv59FeDIM0c@public.gmane.org \
--cc=arve-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=benjamin.gaignard-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=brauner-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
--cc=corbet-T1hC0tSOHrs@public.gmane.org \
--cc=daniel-/w4YWyX8dFk@public.gmane.org \
--cc=hridya-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=joel-QYYGw3jwrUn5owFQY34kdNi2O/JbrIOy@public.gmane.org \
--cc=labbott-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=lmark-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=maarten.lankhorst-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=maco-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=mripard-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sumit.semwal-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=surenb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tjmercier-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=tkjos-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=tzimmermann-l3A5Bk7waGM@public.gmane.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.