Proposal to report GPU private memory allocations with sysfs nodes [plain text version]
Pekka Paalanen
ppaalanen at gmail.com
Fri Nov 1 08:36:57 UTC 2019
On Thu, 31 Oct 2019 13:57:00 -0400
Kenny Ho <y2kenny at gmail.com> wrote:
> Hi Yiwei,
>
> This is the latest series:
> https://patchwork.kernel.org/cover/11120371/
>
> (I still need to reply some of the feedback.)
>
> Regards,
> Kenny
>
> On Thu, Oct 31, 2019 at 12:59 PM Yiwei Zhang <zzyiwei at google.com> wrote:
> >
> > Hi Kenny,
> >
> > Thanks for the info. Do you mind forwarding the existing discussion to me or have me cc'ed in that thread?
> >
> > Best,
> > Yiwei
> >
> > On Wed, Oct 30, 2019 at 10:23 PM Kenny Ho <y2kenny at gmail.com> wrote:
> >>
> >> Hi Yiwei,
> >>
> >> I am not sure if you are aware, there is an ongoing RFC on adding drm
> >> support in cgroup for the purpose of resource tracking. One of the
> >> resource is GPU memory. It's not exactly the same as what you are
> >> proposing (it doesn't track API usage, but it tracks the type of GPU
> >> memory from kmd perspective) but perhaps it would be of interest to
> >> you. There are no consensus on it at this point.
Hi Yiwei,
I'd like to point out an effort to have drivers label BOs for debugging
purposes: https://lists.freedesktop.org/archives/dri-devel/2019-October/239727.html
I don't know if it would work, but an obvious idea might be to use
those labels for tracking the kinds of buffers - a piece of UAPI which I
believe you are still missing.
Thanks,
pq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20191101/b3c5dfd6/attachment.sig>
More information about the dri-devel
mailing list