From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
thomas.hellstrom@linux.intel.com, nouveau@lists.freedesktop.org,
jani.nikula@linux.intel.com, kherbst@redhat.com,
lyude@redhat.com, zackr@vmware.com
Subject: Rework TTMs busy handling
Date: Thu, 4 Jan 2024 16:05:41 +0100 [thread overview]
Message-ID: <20240104150545.1483-1-christian.koenig@amd.com> (raw)
Hi guys,
I'm trying to make this functionality a bit more useful for years now
since we multiple reports that behavior of drivers can be suboptimal
when multiple placements be given.
So basically instead of hacking around the TTM behavior in the driver
once more I've gone ahead and changed the idle/busy placement list
into idle/busy placement flags. This not only saves a bunch of code,
but also allows setting some placements as fallback which are used if
allocating from the preferred ones didn't worked.
Intel CI seems to be happy with those patches, so any more comments?
Regards,
Christian.
next reply other threads:[~2024-01-04 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 15:05 Christian König [this message]
2024-01-04 15:05 ` [PATCH 1/4] drm/ttm: return ENOSPC from ttm_bo_mem_space Christian König
2024-01-04 15:05 ` [PATCH 2/4] drm/ttm: replace busy placement with flags v4 Christian König
2024-01-04 20:02 ` Zack Rusin
2024-01-05 12:27 ` Christian König
2024-01-04 15:05 ` [PATCH 3/4] drm/ttm: improve idle/busy handling v2 Christian König
2024-01-04 15:05 ` [PATCH 4/4] drm/amdgpu: use GTT only as fallback for VRAM|GTT Christian König
-- strict thread matches above, loose matches on Subject: below --
2024-01-09 7:47 Rework TTMs busy handling Christian König
2024-01-09 8:14 ` Thomas Hellström
2024-01-09 8:34 ` Christian König
2024-01-10 9:03 ` Michel Dänzer
2024-01-12 12:51 Christian König
2024-01-16 9:57 ` Christian König
2024-01-17 3:13 ` Zack Rusin
2024-01-26 14:09 Christian König
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=20240104150545.1483-1-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kherbst@redhat.com \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=zackr@vmware.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 read-only IMAP folder(s) and NNTP newsgroup(s).