From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: [PATCH 0/2] drm/xe: Avoid unnecessary OOM kills
Date: Thu, 17 Oct 2024 16:44:05 +0200 [thread overview]
Message-ID: <20241017144407.91919-1-thomas.hellstrom@linux.intel.com> (raw)
On kernel memory allocations where invoking the OOM killer is to be
avoided, but trying pretty hard to fulfill the allocation is still
desirable, one can use __GFP_RETRY_MAYFAIL.
Use that for buffer memory allocation-and validation and for
multiple bind memory allocation.
Thomas Hellström (2):
drm/xe: Avoid the OOM killer on buffer object memory allocation
drm/xe: Don't unnecessarily invoke the OOM killer on multiple binds
drivers/gpu/drm/xe/xe_bo.c | 9 ++++++++-
drivers/gpu/drm/xe/xe_vm.c | 8 ++++----
2 files changed, 12 insertions(+), 5 deletions(-)
--
2.46.0
next reply other threads:[~2024-10-17 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 14:44 Thomas Hellström [this message]
2024-10-17 14:44 ` [PATCH 1/2] drm/xe: Avoid the OOM killer on buffer object memory allocation Thomas Hellström
2024-10-17 14:55 ` Matthew Brost
2024-10-17 14:44 ` [PATCH 2/2] drm/xe: Don't unnecessarily invoke the OOM killer on multiple binds Thomas Hellström
2024-10-17 14:52 ` Matthew Brost
2024-10-17 15:08 ` ✓ CI.Patch_applied: success for drm/xe: Avoid unnecessary OOM kills Patchwork
2024-10-17 15:08 ` ✓ CI.checkpatch: " Patchwork
2024-10-17 15:09 ` ✓ CI.KUnit: " Patchwork
2024-10-17 15:21 ` ✓ CI.Build: " Patchwork
2024-10-17 15:23 ` ✓ CI.Hooks: " Patchwork
2024-10-17 15:24 ` ✓ CI.checksparse: " Patchwork
2024-10-17 15:48 ` ✓ CI.BAT: " Patchwork
2024-10-18 4:39 ` ✗ CI.FULL: failure " Patchwork
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=20241017144407.91919-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox