From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-188.mta1.migadu.com (out-188.mta1.migadu.com [95.215.58.188]) (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 EE8143B71BE for ; Tue, 7 Jul 2026 19:48:25 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.188 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783453707; cv=none; b=QR4ifG8Nk3Bxl3/XSAFWzqznM0dwhvQ2n+i16SmfkUbjxuqJR1nf81ZbQrtA3cDZdyEkohIkrPpzKmqJnXOkeExY6g+LuK65mxwJCF7b8iAE7jU940gEHF24PCoXbpkByA9M98oy6ZDj10vshjc+rVa9CD84n/4BOHJDUxybWao= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783453707; c=relaxed/simple; bh=jTibTs6zBtiy5rariY5pHT8U23V2599t3yWOOUj04fs=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ZQfuDSfreeWAtW/ai+msv6+0xTEO4NZHoe1R/fPpyTPWMh+XvrNw1/BNY7iidF8STSS+CTU1/m77363XkUn9IzbbftBsHEp0Q+PLKmdD7ZSCpfzH43cFbBfKADGBhSAetErVmuaXaVxkaccqJkjWlRJulshe+dO0pHNec9KadiY= 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=ts+EhNAt; arc=none smtp.client-ip=95.215.58.188 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="ts+EhNAt" Date: Tue, 7 Jul 2026 12:48:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1783453703; 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=w6YdfinE5Y+gd0K7HnYdBuEHkj0MV+94snnoeWtOoto=; b=ts+EhNAtWEHYnnXybG3Wwt1iiidVRm+7gyatv3dOousgSi3tqLDNvwRcicdMGKxA337aKI 1ckftnguaMosnMOhatU2126ySVCnWfLr1gHqAb3Bhq+j2SD9ICGaMp7Z6h9cGxAaOAAIp0 Q1w+A3G4+M6mQFMNLaJznQHkn1MCCzQ= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Shakeel Butt To: Richard Chang Cc: Andrew Morton , Kairui Song , Qi Zheng , Barry Song , Axel Rasmussen , Yuanchu Xie , Wei Xu , Johannes Weiner , David Hildenbrand , Michal Hocko , Lorenzo Stoakes , Suren Baghdasaryan , "T . J . Mercier" , Martin Liu , Minchan Kim , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm: vmscan: abort proactive reclaim early when freezing Message-ID: References: <20260706081218.3438762-1-richardycc@google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20260706081218.3438762-1-richardycc@google.com> X-Migadu-Flow: FLOW_OUT On Mon, Jul 06, 2026 at 08:12:18AM +0000, Richard Chang wrote: > Proactive reclaim (via memory.reclaim or node reclaim) checks for pending > signals in its outer loop in user_proactive_reclaim(). However, the inner > reclaim loops—scanning cgroups in shrink_many() and evicting folios in > try_to_shrink_lruvec() can run for a long time before returning to the > outer loop, especially on systems with many cgroups or large memory sizes. > > This latency in responding to signals can block the freezer (both cgroup > freezer and system suspend), leading to freezer timeouts. This issue was > specifically observed on Android when attempting to freeze background > cgroups while proactive reclaim was active. > Can you please explain how freezing operation was delayed due to proactive reclaim?