From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Tejas Upadhyay <tejas.upadhyay@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH 0/7] drm/xe: fdinfo memory stats
Date: Thu, 7 Sep 2023 14:52:29 +0530 [thread overview]
Message-ID: <58217dd8-e733-47e1-adbc-95186f01ba3d@intel.com> (raw)
In-Reply-To: <20230831090536.2949934-1-tejas.upadhyay@intel.com>
On 31-08-2023 14:35, Tejas Upadhyay wrote:
> This series enables enables fdinfo memory stats for xe.
>
> I added tracking of most classes of bo (user bo, page tables, ring, lrc)
> which contribute to client's memory usage. This follows similar lines to
> what Rob's msm code and tvrtko's i915 code is doing with some xe way
> of showing and tracking/fecthing objects which adds to client memory
> stats.
>
> Example fdinfo format:
>
> #cat /proc/4620/fdinfo/3
> pos: 0
> flags: 0100002
> mnt_id: 23
> ino: 1116
> drm-driver: xe
> drm-client-id: 13
> drm-pdev: 0000:4d:00.0
> drm-total-system: 0
> drm-shared-system: 0
> drm-active-system: 0
> drm-resident-system: 0
> drm-purgeable-system: 0
> drm-total-gtt: 4 KiB
> drm-shared-gtt: 0
> drm-active-gtt: 0
> drm-resident-gtt: 4 KiB
> drm-purgeable-gtt: 0
> drm-total-vram0: 20 KiB
> drm-shared-vram0: 0
> drm-active-vram0: 0
> drm-resident-vram0: 20 KiB
> drm-purgeable-vram0: 0
> drm-total-vram1: 20 KiB
> drm-shared-vram1: 0
> drm-active-vram1: 0
> drm-resident-vram1: 20 KiB
> drm-purgeable-vram1: 0
drm-purgeable-vram0, drm-purgeable-vram1 ?
Are they correct entries ? Seems issue in PATCH7.
BR
Himal
>
> Signed-off-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
>
> Tejas Upadhyay (7):
> drm/xe: Add drm-client infrastructure
> drm/xe: Interface xe drm client with fdinfo interface
> drm/xe: Add tracking support for bos per client
> drm/xe: Record each drm client with its VM
> drm/xe: Track page table memory usage for client
> drm/xe: Account ring buffer and context state storage
> drm/xe: Implement fdinfo memory stats printing
>
> drivers/gpu/drm/xe/Makefile | 1 +
> drivers/gpu/drm/xe/xe_bo.c | 7 +
> drivers/gpu/drm/xe/xe_bo.h | 11 ++
> drivers/gpu/drm/xe/xe_bo_types.h | 10 ++
> drivers/gpu/drm/xe/xe_device.c | 19 ++-
> drivers/gpu/drm/xe/xe_device_types.h | 6 +
> drivers/gpu/drm/xe/xe_drm_client.c | 228 +++++++++++++++++++++++++++
> drivers/gpu/drm/xe/xe_drm_client.h | 71 +++++++++
> drivers/gpu/drm/xe/xe_lrc.c | 7 +-
> drivers/gpu/drm/xe/xe_pt.c | 4 +-
> drivers/gpu/drm/xe/xe_vm.c | 10 +-
> drivers/gpu/drm/xe/xe_vm_types.h | 2 +
> 12 files changed, 372 insertions(+), 4 deletions(-)
> create mode 100644 drivers/gpu/drm/xe/xe_drm_client.c
> create mode 100644 drivers/gpu/drm/xe/xe_drm_client.h
>
next prev parent reply other threads:[~2023-09-07 9:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 9:05 [Intel-xe] [PATCH 0/7] drm/xe: fdinfo memory stats Tejas Upadhyay
2023-08-31 9:05 ` [Intel-xe] [PATCH 1/7] drm/xe: Add drm-client infrastructure Tejas Upadhyay
2023-09-06 4:14 ` Ghimiray, Himal Prasad
2023-09-07 8:57 ` Upadhyay, Tejas
2023-09-12 8:24 ` Ghimiray, Himal Prasad
2023-08-31 9:05 ` [Intel-xe] [PATCH 2/7] drm/xe: Interface xe drm client with fdinfo interface Tejas Upadhyay
2023-09-06 4:21 ` Ghimiray, Himal Prasad
2023-08-31 9:05 ` [Intel-xe] [PATCH 3/7] drm/xe: Add tracking support for bos per client Tejas Upadhyay
2023-09-06 9:38 ` Ghimiray, Himal Prasad
2023-09-07 8:52 ` Upadhyay, Tejas
2023-08-31 9:05 ` [Intel-xe] [PATCH 4/7] drm/xe: Record each drm client with its VM Tejas Upadhyay
2023-09-06 9:47 ` Ghimiray, Himal Prasad
2023-09-07 8:49 ` Upadhyay, Tejas
2023-09-07 9:28 ` Ghimiray, Himal Prasad
2023-09-07 9:44 ` Upadhyay, Tejas
2023-08-31 9:05 ` [Intel-xe] [PATCH 5/7] drm/xe: Track page table memory usage for client Tejas Upadhyay
2023-09-06 9:54 ` Ghimiray, Himal Prasad
2023-09-07 8:40 ` Upadhyay, Tejas
2023-08-31 9:05 ` [Intel-xe] [PATCH 6/7] drm/xe: Account ring buffer and context state storage Tejas Upadhyay
2023-09-06 11:19 ` Ghimiray, Himal Prasad
2023-08-31 9:05 ` [Intel-xe] [PATCH 7/7] drm/xe: Implement fdinfo memory stats printing Tejas Upadhyay
2023-08-31 12:19 ` Upadhyay, Tejas
2023-09-12 6:22 ` Ghimiray, Himal Prasad
2023-09-12 11:14 ` Jani Nikula
2023-08-31 9:21 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: fdinfo memory stats Patchwork
2023-08-31 9:21 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-31 9:22 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-31 9:29 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-31 9:30 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-08-31 9:30 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-31 10:04 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
2023-08-31 11:23 ` Patchwork
2023-09-07 9:22 ` Ghimiray, Himal Prasad [this message]
2023-09-07 9:35 ` [Intel-xe] [PATCH 0/7] " Upadhyay, Tejas
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=58217dd8-e733-47e1-adbc-95186f01ba3d@intel.com \
--to=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=tejas.upadhyay@intel.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