intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Stuart Summers <stuart.summers@intel.com>
Cc: matthew.brost@intel.com, John.C.Harrison@Intel.com,
	brian.welty@intel.com, intel-xe@lists.freedesktop.org,
	rodrigo.vivi@intel.com, Stuart Summers <stuart.summers@intel.com>
Subject: [PATCH 0/2] Update page fault queue size calculation
Date: Thu, 11 Jul 2024 17:36:27 +0000	[thread overview]
Message-ID: <cover.1720718987.git.stuart.summers@intel.com> (raw)

Right now the page fault queue size is hard coded with an
estimated value based on legacy platforms. Add a more precise
calculation based on the number of compute resources available
which can utilize these page fault queues.

v2: Add a drm reset callback for the teardown changes and other
    suggestions from Matt.
v3: Add a pf_wq destroy when the access counter wq allocation
    fails (Rodrigo) and pf queue size calculation adjustment (Matt)

Original series: https://patchwork.freedesktop.org/series/134694/

Stuart Summers (2):
  drm/xe: Fix missing workqueue destroy in xe_gt_pagefault
  drm/xe: Use topology to determine page fault queue size

 drivers/gpu/drm/xe/xe_gt_pagefault.c | 72 ++++++++++++++++++++++------
 drivers/gpu/drm/xe/xe_gt_types.h     |  9 +++-
 2 files changed, 65 insertions(+), 16 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-07-11 17:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 17:36 Stuart Summers [this message]
2024-07-11 17:36 ` [PATCH 1/2] drm/xe: Fix missing workqueue destroy in xe_gt_pagefault Stuart Summers
2024-07-11 17:36 ` [PATCH 2/2] drm/xe: Use topology to determine page fault queue size Stuart Summers
2024-07-11 18:20   ` Cavitt, Jonathan
2024-07-11 19:36     ` Summers, Stuart
2024-07-11 18:32   ` Matthew Brost
2024-07-11 19:36     ` Summers, Stuart
2024-07-16 17:11       ` Matthew Brost
2024-07-16 20:07         ` Summers, Stuart
2024-07-11 17:43 ` ✓ CI.Patch_applied: success for Update page fault queue size calculation (rev2) Patchwork
2024-07-11 17:44 ` ✓ CI.checkpatch: " Patchwork
2024-07-11 17:45 ` ✓ CI.KUnit: " Patchwork
2024-07-11 17:57 ` ✓ CI.Build: " Patchwork
2024-07-11 17:59 ` ✗ CI.Hooks: failure " Patchwork
2024-07-11 18:00 ` ✓ CI.checksparse: success " Patchwork
2024-07-11 18:32 ` ✗ CI.BAT: failure " Patchwork
2024-07-11 20:06 ` ✗ CI.FULL: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-07-09 18:40 [PATCH 0/2] Update page fault queue size calculation Stuart Summers

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=cover.1720718987.git.stuart.summers@intel.com \
    --to=stuart.summers@intel.com \
    --cc=John.C.Harrison@Intel.com \
    --cc=brian.welty@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).