From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from l2mail1.panix.com (l2mail1.panix.com [166.84.1.75]) (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 6A508209F43 for ; Fri, 1 May 2026 19:27:08 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=166.84.1.75 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777663630; cv=none; b=EPQaXu+PMkk1d48pC3x7mJBBxy8ral+A8puF9+McbLD00SLu5GRs3r13C+PrbKU1a2ojgPPN+JzMHPSl1VAwxe7wTYSAagE06yni1U79e5+e5Ey38hevhqMIO/2ofGR54jv/2m17b1T6GvoRP2O/rb/NHRt+20NP8l6ZT8tFQk4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777663630; c=relaxed/simple; bh=l6JbYucB+9yD0k96T5o6k3yiniTY2VGeKOqZ7PJWN2I=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=cEgZ4GdgewQyStQ3vNp5TP5haqqEQ3wNWlbIenEOCIT31kMUq/RbxQpo6GBB0y4jEvHyQx+Sqg/gktbnvw612Y4icnXBNORmsM67gP9dN2ZRwz5nfNtxWGEPMlw3tGlaDam3jFJaMh2AEGfTXu8xDKEll7aovHib8w5IVCOKZh4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=panix.com; spf=pass smtp.mailfrom=panix.com; dkim=pass (1024-bit key) header.d=panix.com header.i=@panix.com header.b=uLrtLc67; arc=none smtp.client-ip=166.84.1.75 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=panix.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=panix.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=panix.com header.i=@panix.com header.b="uLrtLc67" Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (1024 bits) server-digest SHA256) (No client certificate requested) by l2mail1.panix.com (Postfix) with ESMTPS id 4g6gZ20M7hzDSp for ; Fri, 1 May 2026 15:08:58 -0400 (EDT) Received: from [10.50.4.26] (45-31-46-51.lightspeed.sndgca.sbcglobal.net [45.31.46.51]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4g6gYs5wssz40Dc; Fri, 1 May 2026 15:08:49 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=panix.com; s=panix; t=1777662531; bh=l6JbYucB+9yD0k96T5o6k3yiniTY2VGeKOqZ7PJWN2I=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=uLrtLc67iWq4GSqPGwTJ4rzevu63TXdyY+tNy3yIoVxzTdPx+0fPodKpQqxhC4lNc QCHPB1S0lTSGcF0UU4nPVLMx1ZldiL+6j23fwwJohT2SBeEYi26JMpRWvIueKLSTyb EzfKFKOXzZUJmOYybDBlTJSczHHL4DxaWkFQioyw= Message-ID: Date: Fri, 1 May 2026 12:08:48 -0700 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: PATCH v4 0/6] mm, drm/ttm, drm/xe: Avoid reclaim/eviction loops under fragmentation To: Matthew Brost , intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org Cc: =?UTF-8?Q?Thomas_Hellstr=C3=B6m?= , Andrew Morton , David Hildenbrand , Lorenzo Stoakes , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Kenneth C References: <20260430191809.2142544-1-matthew.brost@intel.com> <20260430191809.2142544-3-matthew.brost@intel.com> Content-Language: en-US From: Kenneth Crudup In-Reply-To: <20260430191809.2142544-3-matthew.brost@intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 4/30/26 12:18, Matthew Brost wrote: > Introduce zone_maybe_fragmented_in_shrinker() as a lightweight helper to > allow subsystems to make coarse decisions about reclaim behavior in the > presence of likely fragmentation I'm running Linus' master on my LunarLake (258v) laptop, and sometimes after compiling a kernel (of all things) I'd see kswapd0 thrash despite having quite a bit of free memory. I finally traced it to the xe driver after seeing the "GPUActive" field in /proc/meminfo suddenly start rising, eventually growing larger than real memory by several times (see below). This patchset fixes the issue, and I'm sure there'll be a fix going into Linus' master soon, but what I'M wondering is how could building a kernel (which is just in a KDE Konsole running on Wayland) make the GPActive grow from ~1.6G to > 30G (and continue to rise, RN I'm seeing 91839848 kBs and still growing). -Kenny ---- SwapTotal: 33554428 kB MemTotal: 32345672 kB GPUActive: 652640 kB GPUReclaim: 403988 kB SwapTotal: 33554428 kB MemTotal: 32345672 kB GPUActive: 651180 kB GPUReclaim: 406812 kB SwapTotal: 33554428 kB MemTotal: 32345672 kB GPUActive: 659004 kB GPUReclaim: 399396 kB SwapTotal: 33554428 kB MemTotal: 32345672 kB GPUActive: 666996 kB GPUReclaim: 392764 kB GPUActive: 91832468 kB SwapTotal: 33554428 kB MemTotal: 32345672 kB GPUReclaim: 488000 kB GPUActive: 91832332 kB SwapTotal: 33554428 kB MemTotal: 32345672 kB GPUReclaim: 487988 kB GPUActive: 91869376 kB SwapTotal: 33554428 kB MemTotal: 32345672 kB GPUReclaim: 486504 kB ---- -- Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA