From: Alex Deucher <alexdeucher@gmail.com>
To: Alex Deucher <alexander.deucher@amd.com>
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/2] fdinfo shared stats
Date: Fri, 5 Jan 2024 16:03:12 -0500 [thread overview]
Message-ID: <CADnq5_O4FERKSD9D3uxPQx1RB4NJ+krQEC-WfZBZzFNceAUZEw@mail.gmail.com> (raw)
In-Reply-To: <CADnq5_PdmDWyJsDvtvCbNguExt2aydXy_rZOPHii5imMtt_Z+A@mail.gmail.com>
Ping on this series again?
Alex
On Wed, Dec 13, 2023 at 4:13 PM Alex Deucher <alexdeucher@gmail.com> wrote:
>
> On Thu, Dec 7, 2023 at 1:03 PM Alex Deucher <alexander.deucher@amd.com> wrote:
> >
> > We had a request to add shared buffer stats to fdinfo for amdgpu and
> > while implementing that, Christian mentioned that just looking at
> > the GEM handle count doesn't take into account buffers shared with other
> > subsystems like V4L or RDMA. Those subsystems don't use GEM, so it
> > doesn't really matter from a GPU top perspective, but it's more
> > correct if you actually want to see shared buffers.
>
> Any thoughts on this? Seem reasonable?
>
> Alex
>
> >
> > Alex Deucher (2):
> > drm: update drm_show_memory_stats() for dma-bufs
> > drm/amdgpu: add shared fdinfo stats
> >
> > drivers/gpu/drm/amd/amdgpu/amdgpu_fdinfo.c | 4 ++++
> > drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 11 +++++++++++
> > drivers/gpu/drm/amd/amdgpu/amdgpu_object.h | 6 ++++++
> > drivers/gpu/drm/drm_file.c | 2 +-
> > 4 files changed, 22 insertions(+), 1 deletion(-)
> >
> > --
> > 2.42.0
> >
prev parent reply other threads:[~2024-01-05 21:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 18:02 [PATCH 0/2] fdinfo shared stats Alex Deucher
2023-12-07 18:02 ` [PATCH 1/2] drm: update drm_show_memory_stats() for dma-bufs Alex Deucher
2023-12-07 18:02 ` Alex Deucher
2023-12-13 21:28 ` Felix Kuehling
2024-01-08 17:29 ` Rob Clark
2023-12-07 18:02 ` [PATCH 2/2] drm/amdgpu: add shared fdinfo stats Alex Deucher
2023-12-07 18:02 ` Alex Deucher
2024-01-08 21:27 ` Alex Deucher
2024-01-09 7:56 ` Christian König
2024-01-09 7:56 ` Christian König
2024-01-09 9:30 ` Tvrtko Ursulin
2024-01-09 12:54 ` Daniel Vetter
2024-01-09 12:54 ` Daniel Vetter
2024-01-09 13:25 ` Tvrtko Ursulin
2024-01-09 13:25 ` Tvrtko Ursulin
2024-01-09 14:26 ` Daniel Vetter
2024-01-09 14:26 ` Daniel Vetter
2024-01-09 14:57 ` Christian König
2024-01-09 14:57 ` Christian König
2024-01-09 15:09 ` Tvrtko Ursulin
2024-01-09 15:09 ` Tvrtko Ursulin
2023-12-13 21:13 ` [PATCH 0/2] fdinfo shared stats Alex Deucher
2024-01-05 21:03 ` Alex Deucher [this message]
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=CADnq5_O4FERKSD9D3uxPQx1RB4NJ+krQEC-WfZBZzFNceAUZEw@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.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.