When the TTM pool tries to allocate new pages, it stats with max order. If there are no pages ready in the system, the page allocator will start reclaim. If direct reclaim fails, the allocator will reduce the order until it gets all the pages it wants with whatever order the allocator succeeds to reclaim.
However, while the allocator is reclaiming, lower order pages might be available, which would work just fine for the pool allocator. Doing direct reclaim just introduces latency in allocating memory. The system should still start reclaiming in the background with kswapd, but the pool allocator should try to allocate a lower order page instead of directly reclaiming. If not even a order-1 page is available, the TTM pool allocator will eventually get to start allocating order-0 pages, at which point it should and will directly reclaim. Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]> --- drivers/gpu/drm/ttm/ttm_pool.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/ttm/ttm_pool.c b/drivers/gpu/drm/ttm/ttm_pool.c index baf27c70a4193a121fbc8b4e67cd6feb4c612b85..6124a53cd15634c833bce379093b557d2a2660fd 100644 --- a/drivers/gpu/drm/ttm/ttm_pool.c +++ b/drivers/gpu/drm/ttm/ttm_pool.c @@ -144,9 +144,11 @@ static struct page *ttm_pool_alloc_page(struct ttm_pool *pool, gfp_t gfp_flags, * Mapping pages directly into an userspace process and calling * put_page() on a TTM allocated page is illegal. */ - if (order) + if (order) { gfp_flags |= __GFP_NOMEMALLOC | __GFP_NORETRY | __GFP_NOWARN | __GFP_THISNODE; + gfp_flags &= ~__GFP_DIRECT_RECLAIM; + } if (!pool->use_dma_alloc) { p = alloc_pages_node(pool->nid, gfp_flags, order); --- base-commit: b320789d6883cc00ac78ce83bccbfe7ed58afcf0 change-id: 20250909-ttm_pool_no_direct_reclaim-ee0807a2d3fe Best regards, -- Thadeu Lima de Souza Cascardo <[email protected]>
