diff options
| author | Matthew Brost <matthew.brost@intel.com> | 2026-06-12 15:57:57 -0700 |
|---|---|---|
| committer | Matthew Brost <matthew.brost@intel.com> | 2026-06-13 17:30:33 -0700 |
| commit | a56a73ec85c81c7e533bc249ff0fd996256053fd (patch) | |
| tree | e482aa746e5bd8c003b701dec45830611165d401 /tools/perf/scripts/python | |
| parent | 2afdfc658f7a7e9ee2a67ec6663922da9c799c53 (diff) | |
drm/ttm: Issue direct reclaim at beneficial_order
Triggering kswap at an order higher than beneficial_order makes little
sense, as the driver has already indicated the optimal order at which
reclaim is effective. Similarly, issuing direct reclaim or triggering
kswap at a lower order than beneficial_order is ineffective, since the
driver does not benefit from reclaiming lower-order pages.
As a result, direct reclaim should only be issued with __GFP_NORETRY at
exactly beneficial_order, or as a fallback, direct reclaim without
__GFP_NORETRY at order 0 when failure is not an option.
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Christian Koenig <christian.koenig@amd.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Link: https://patch.msgid.link/20260612225757.3844350-1-matthew.brost@intel.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
