From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-183.mta1.migadu.com (out-183.mta1.migadu.com [95.215.58.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7C48F27FB0E for ; Sat, 9 May 2026 02:31:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.183 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778293906; cv=none; b=mhOntLgNS21si0kbwMdxuCXlXh62OTpKiZJX8YRNp22cu0RjSyKVyKPSErfQ6saC0dVeJH9jByVCQL1PPe9+PkRxCSjEQMSWh/nxrDfGWCRbLarNfQL1mOBiZzERmWGpTZzGu/E6uKsSUigFYnsooujFiCsru97O9UeMttYTSR0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778293906; c=relaxed/simple; bh=xEEuI5KAeTF6LB+t5A3f1n4seM4KiSyvLOTumXsln78=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=rVb9AzWVAoZVWqOmV4vCUegjSQ0ovcMQ1vmDAE+Qd2j93YL39FwjgWE5kIeiIwF13wOFG1fob24IMU0YOkoLvUL9yHUX0e1LDBJhMo6Ym2YA+nXiqQBATs9nXXW+8iJKDNmoXd2KCzHoH4v2ExF9muumGQDtwvnRrxD3vwEfG8Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=t7OBeIUy; arc=none smtp.client-ip=95.215.58.183 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="t7OBeIUy" Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1778293900; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=isoMVqmiA39mM7GIpQVXu+Zu5R5lf1TBBevgqgkjmOE=; b=t7OBeIUyKK8fXSiN+xna9GkR7p4NwqefMbij1e8D74GOypyjdZDkhoArPhuZVaLhL59w/0 JQgmkV8WJTeALVBdGfHmqe+M6Yg/X5UDJ3GmG14SQvxKPFrA68miMpu1o1BtToCsSNDYK5 9+Dlr2RHsXkZlRF1zG1jBTqfzlJSJW0= Date: Sat, 9 May 2026 10:31:15 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v5 0/5] mm, drm/ttm, drm/xe: Avoid reclaim/eviction loops under fragmentation To: Andrew Morton , Matthew Brost , Dave Chinner Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org, Qi Zheng , Roman Gushchin , Johannes Weiner , Shakeel Butt , Kairui Song , Barry Song , Axel Rasmussen , Yuanchu Xie , Wei Xu , Tvrtko Ursulin , =?UTF-8?Q?Thomas_Hellstr=C3=B6m?= , Carlos Santa , Christian Koenig , Huang Rui , Matthew Auld , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Daniel Colascione , David Hildenbrand , Lorenzo Stoakes , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , linux-mm@kvack.org, linux-kernel@vger.kernel.org References: <20260506033300.3534883-1-matthew.brost@intel.com> <20260508170355.c937b91cdd63a11e56d2225d@linux-foundation.org> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Qi Zheng In-Reply-To: <20260508170355.c937b91cdd63a11e56d2225d@linux-foundation.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 5/9/26 8:03 AM, Andrew Morton wrote: > On Tue, 5 May 2026 20:32:55 -0700 Matthew Brost wrote: > >> TTM allocations at higher orders can drive Xe into a pathological >> reclaim loop when memory is fragmented: >> >> ... >> >> This series addresses the issue in three layers: > > Thanks. AI review asked a few things, nothing looked very serious to > my eye: > > https://sashiko.dev/#/patchset/20260506033300.3534883-1-matthew.brost@intel.com I recall Dave having concerns about the design itself in v4 [1], but since he wasn't CC'ed on the whole patchset, there seems to be no further conclusion. Maybe it's best to wait for his further feedback. ;) [1]. https://lore.kernel.org/all/afQE-2JOzfOm8enM@dread/