https://bugs.kde.org/show_bug.cgi?id=444042

David Redondo <k...@david-redondo.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |k...@david-redondo.de,
                   |                            |k...@davidedmundson.co.uk

--- Comment #1 from David Redondo <k...@david-redondo.de> ---
Thanks for contacting us. In fact those two things are also something we are
interested in!

When writing the new system monitor we also looked into how we could get gpu
statistics, both total and and per PID.

For global engine  and vram usage we have abstractions in place to support
different code paths for different vendors.
For example on AMD we read some sysfs files or on Nvidia run nvidia-smi.
Unfortunately we couldn't figure out a way to get global usage info for Intel
GPUs . We concluded that we would require privileges for accessing perf events
across all pids (as would running intel_gpu_top and parsing output).
(I just rechecked and apprarently now you only CAP_PERFMON instead of
CAP_SYS_ADMIN, so maybe we have an oppportunity here with a helper binary like
we do for per  process network speeds?)


A standard interface for per process GPU would indeed be amazing!
We can extend process info dynamically via plugins although
right now we only have one for nvidia which is running nvidia-smi in a
different mode...
We actually found one of your earlier patches for this during research
https://lists.freedesktop.org/archives/intel-gfx/2020-September/248062.html and
hoped for something like this for the future.
>From glancing at your series am I right, that amdgpu already uses such an
interface like you are proposing but it's not documented?

I think I can also speak for the other plasma-systemmonitor developers  that we
are happy to collaborate. We are also available on #plasma, feel free to ping
us (DavidRedondo, d_ed or ahiemstra) for a more real time conversation

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to