From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pg1-f176.google.com (mail-pg1-f176.google.com [209.85.215.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A8A2F1A9FA0 for ; Tue, 21 Apr 2026 02:01:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.215.176 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776736917; cv=none; b=fgiOVzYGVJhOjfbkfsvEiDnih3bFaRXLmv+uvGicLcI0IHYhxjHomqfG6qIhq4wg/LnQITYYSafHSMYpmE66pGXtR4mgTgjb1HPqVWmx4f7Im8qPiWpYaoVgOTGwk361Fm9EtWTjviWmtRNmGlhzNFUZtYgSrM804eihLADEA+0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776736917; c=relaxed/simple; bh=l9bRz9UeCPAV9DA8Zy5r0ie/prB1/Xr8Z+QnqVjykhA=; h=From:To:Cc:Subject:In-Reply-To:Date:Message-ID:References; b=YTksbPcsLw6S5nA/qaMckbJFGYgVDw3SFRcGL1YxeEfQBa39tBVojBaxnSuteABEZydwpo2VpbOi4Pj9MarR1uLk6nJoYBunUG+HmVl94Jf+F64Qai6ELZ9jK+uBLIfpIWSiAgjUC1rB71hNm1sYaoh6QFbioCD0ZqHl4uufYTI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=XskVbg+B; arc=none smtp.client-ip=209.85.215.176 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="XskVbg+B" Received: by mail-pg1-f176.google.com with SMTP id 41be03b00d2f7-c648bc907ebso2403147a12.3 for ; Mon, 20 Apr 2026 19:01:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1776736915; x=1777341715; darn=vger.kernel.org; h=references:message-id:date:in-reply-to:subject:cc:to:from:from:to :cc:subject:date:message-id:reply-to; bh=HAfyiA5fxqYXT4gYRX9zfWikwnCgQwE5e6No9OGkL8Y=; b=XskVbg+BJsj32X8H+Rf6+BXY8Llvyd4yvTB+mmbWcDkA4v3GBhKwVjRazy9zkOig2F AU6Fkl9QCa2PEDPsghPR4e3v64RfZoq7mjp8DkxoGFQv/yfhWgiDQZ4umrmGHfjos8Nj 7B0KwN9ejXrLewIz+edRFUmOl8F81dtnlpQV6qAkW1NfsS8s3xh1PZgbRHfwA12NxAUy fL4Xm3DisCW9om0yRpixnwxFLAjdgLCakxCQDVMatIqYPxBSiRZaNsfDNI5N1aMuiQz9 38EozjmEDteXe24b68MG4VTErQ64u7m8Hu7zJNcVw3DJb05GLVtll5pTE+PxUUBpkSpz cEKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776736915; x=1777341715; h=references:message-id:date:in-reply-to:subject:cc:to:from:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=HAfyiA5fxqYXT4gYRX9zfWikwnCgQwE5e6No9OGkL8Y=; b=RX+m+DyueAGyFEaKhl2NkpKOBuT5IgjdMxN1aQS6Rcru2VVRudzRVAUSvNoqTjNoF4 IGHBZEgTdsOyaWM6EJEtZvlMuCKsmwnbuBujxuxnL6QXi/Xv8cT1N9x0zXtEWg2zF5Fw wAavY37DUYYCFSp/uCQhiPG7HVSeLSDgIAzSI/qWt1XUKVo4DKwCZbbEUaw42ufblQe7 wU91JTtybYKKF6xRO8jV5odJDvjm9bCOMpt8FDMyONcg44fbapWeFMcHvW3K8yUyYEdn pIsxqVAbzbjvQ6gmWGuLZnKztNupf1yWuKkRbv3QO5NnU6LAaD2gqrk6PfpJEUBtMtL+ vYfg== X-Forwarded-Encrypted: i=1; AFNElJ+v8d00Qpl6El7vQKVzoVwVeQWg6VLsM1x0RyHoGJQV5iWu4lpTdrjWjrN0mQQB/pgqlfN7g4U=@vger.kernel.org X-Gm-Message-State: AOJu0Yx9fGnco+vdYhi69OGcVwtfyHqa02w4AAAyvpMBtFPuZU1+cZ6f sEsnKi2KG7GOI31gZ5ANR2/ng/fB2jh/XEtE4BYG5sDo27+PsvmK4NrvqLew5w== X-Gm-Gg: AeBDiev6LCDwJogssOGEcv9eJBr1S0Ne9Jr7LGjihUmtP72l7rnVZL2fLxnEQYp5sis T/stV/BF/RjCryO2i8RF/ndlk1ImYj0F81svE6bZCeG/sAqzXPBPzsvwmOE4xO8y3uoVU+OG+Uq jsLiPHKJNiRyoeLGZmLFYbW7GKq1I47R5RV3inAnexFZ2Xs8KBPXB7/73I7lr9ymndEwdMuQvvE VPklp6dagXtmRJ8eHRW7D/wgyJM+ZG1y5Pruq6EJfmsX9k7jQMOUcgWhsHBNly/JaiXhbIcFLNy eO6aEyhrUWK+A8wzFCc1pPtKBwMDUk+KKXwkIMCB2r1h3YVVaMq9xhuAkDce10MQWl/v1q8LB4+ 3xAmHZ4VoP73VNY4Bblua5NlXtvoLGRIuthz6rqYiKCfljU9jahNDqbceeCyXVFXHM938EsjMTI Um9OS8Y8mpXyiEVEQy7l8zpFP7693b+/WP X-Received: by 2002:a17:903:1988:b0:2b4:5cea:f618 with SMTP id d9443c01a7336-2b5f9e7823fmr164463225ad.3.1776736915460; Mon, 20 Apr 2026 19:01:55 -0700 (PDT) Received: from pve-server ([49.205.216.49]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-2b5fa9ff3b4sm149129515ad.2.2026.04.20.19.01.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Apr 2026 19:01:54 -0700 (PDT) From: Ritesh Harjani (IBM) To: Salvatore Dipietro Cc: Matthew Wilcox , abuehaze@amazon.de, alisaidi@amazon.com, blakgeof@amazon.com, brauner@kernel.org, dipietro.salvatore@gmail.com, djwong@kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-xfs@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 1/1] iomap: avoid compaction for costly folio order allocation In-Reply-To: Date: Tue, 21 Apr 2026 06:46:19 +0530 Message-ID: References: <20260420163328.22104-1-dipiets@amazon.it> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Matthew Wilcox writes: > On Mon, Apr 20, 2026 at 04:33:28PM +0000, Salvatore Dipietro wrote: >> I have submitted a v2 of the patch based on Ritesh's suggestion. >> https://lore.kernel.org/linux-mm/20260420161404.642-1-dipiets@amazon.it/T/#u > > ... but without linking back to this thread, so nobody who was exposed > to that thread for the first time knows about this one. That's poor form. Yup. Also, given the Maintainers (willy, Christoph, Dave) shown their dis-interest in taking the patch in it's current form, the right way is to get back with performance data with both the approaches (which we were discussing) and first get the consensus from everyone, before proposing this as a patch :). Having said that, we do care if a genuine performance issue gets reported. In that context, I wanted to understand your setup a bit from memory fragmentation perspective. Are you trying to simulate memory fragmentation and then benchmarking? Or was this problem hitting when you run simply run the reproduction steps mentioned in your cover letter? BTW - I was following the other thread too where PREEMPT_LAZY problem was getting discussed. And from what I understood, you mentioned [1] enabling THP on the system made that problem go away. Also it looks like enabling THP is the right thing to do for this kind of workload. Does that also mean enabling THP fixed this problem too? Do you still hit memory fragmentation and/or similar throughput drop w/o this fix after you enable THP? It will be good to know those details too please. [1]: https://lore.kernel.org/all/20260403191942.21410-1-dipiets@amazon.it/T/#md88ca4258766e897e432df85874d197db476c7d1 -ritesh