From: Rohan Garg <rohan.garg@collabora.com>
To: dri-devel@lists.freedesktop.org, Yiwei Zhang <zzyiwei@google.com>
Cc: Alistair Delva <adelva@google.com>,
Prahlad Kilambi <prahladk@google.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Jerome Glisse <jglisse@redhat.com>, Kenny Ho <y2kenny@gmail.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Sean Paul <seanpaul@chromium.org>,
Chris Forbes <chrisforbes@google.com>,
Android Kernel Team <kernel-team@android.com>
Subject: Re: Proposal to report GPU private memory allocations with sysfs nodes [plain text version]
Date: Thu, 19 Dec 2019 17:18:13 +0100 [thread overview]
Message-ID: <2981882.gi1CFgH74X@saphira> (raw)
In-Reply-To: <CAKT=dDkGCKuE=CNr=9dfXCZw-exc570cc67w_uV_X322cGf3Og@mail.gmail.com>
Hey
> Is it reasonable to add another ioctl or something equivalent to label
> a BO with what PID makes the allocation? When the BO gets shared to
> other processes, this information also needs to be bookkept somewhere
> for tracking. Basically I wonder if it's possible for upstream to
> track BOs in a similar way Android tracks dmabuf. Then there's a node
> implemented by cgroup in proc listing all the BOs per process with
> information like label, refcount, etc. Then Android GPU vendors can
> implement the same nodes which is going to be compatible even if they
> later adopts drm subsystem.
>
> So my sketch idea for the nodes are:
> (1) /proc/gpu0_meminfo, /proc/gpu1_meminfo
> This is a list of all BOs with pids holding a reference to it and the
> current label of each BO
> (2) /proc/<pid>/gpu0_meminfo, /proc/<pid>/gpu1_meminfo
> This is a list of all BOs this process holds a reference to.
> (3) Is it reasonable to implement another nodes for {total,
> total_unmapped} counters? or just surface through /proc/meminfo?
>
This would be tricky to implement because:
(1) PID's are not unique, PID namespaces allow linux userspace to potentially
share the same PID.
(2) Specifically in the case of mesa, there isn't a way to (AFAIK) associate a
BO with a PID.
Cheers
Rohan Garg
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-12-19 16:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 18:35 Proposal to report GPU private memory allocations with sysfs nodes [plain text version] Yiwei Zhang
2019-10-28 15:26 ` Jerome Glisse
2019-10-28 18:33 ` Yiwei Zhang
2019-10-29 1:19 ` Yiwei Zhang
2019-10-31 5:23 ` Kenny Ho
2019-10-31 16:59 ` Yiwei Zhang
2019-10-31 17:57 ` Kenny Ho
2019-11-01 8:36 ` Pekka Paalanen
2019-11-04 19:34 ` Yiwei Zhang
2019-11-05 9:47 ` Daniel Vetter
2019-11-05 19:45 ` Yiwei Zhang
2019-11-06 9:56 ` Daniel Vetter
2019-11-06 16:55 ` Rob Clark
2019-11-06 19:21 ` Yiwei Zhang
2019-11-12 18:17 ` Yiwei Zhang
2019-11-12 20:18 ` Jerome Glisse
2019-11-15 1:02 ` Yiwei Zhang
2019-12-13 22:09 ` Yiwei Zhang
2019-12-19 16:18 ` Rohan Garg [this message]
2019-12-19 18:52 ` Yiwei Zhang
2020-01-06 10:46 ` Rohan Garg
2020-01-06 20:47 ` Yiwei Zhang
2020-03-20 12:07 ` Rohan Garg
2020-03-20 21:35 ` Yiwei Zhang
2019-10-29 8:33 ` Pekka Paalanen
2019-10-30 21:03 ` Yiwei Zhang
2019-10-30 22:06 ` Yiwei Zhang
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=2981882.gi1CFgH74X@saphira \
--to=rohan.garg@collabora.com \
--cc=adelva@google.com \
--cc=chrisforbes@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.com \
--cc=kernel-team@android.com \
--cc=kraxel@redhat.com \
--cc=prahladk@google.com \
--cc=seanpaul@chromium.org \
--cc=y2kenny@gmail.com \
--cc=zzyiwei@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