Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp2628814pxb; Tue, 21 Sep 2021 04:19:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxiFGyPpvNfmDYJlPzXDhzlKJBfD5c58Mqh4QQ+wHogIh3cwsQf9zCA2j3/8HifyADi/bBI X-Received: by 2002:a05:6e02:1c2e:: with SMTP id m14mr4232575ilh.23.1632223168652; Tue, 21 Sep 2021 04:19:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632223168; cv=none; d=google.com; s=arc-20160816; b=iJPUv0F8hgm/LvewDtwjIFuLeSq0Ghh3EpLhq0jAwKWtOXEihgX6wBomhXkpAwgVmf dfzuqUznE417sP0yvy1MH5I7ZG9VgUWN+vGI5d0VAJnBfvhVoo9Lb1ZQKF2noJ58zHy+ yVjVa0TUgiOu0lDeJ5p+Cuy+0P6wwaRRHWInA+qyHvZncT8j2wduipIsIb8P+tOKWSQu nPa2JshMmOr54ITfCkyAuW7Sz/FF/beLtMlFu0J3mSEWxOVdNyo7/ZK8iCkl058wpSjb YRG1FAEwv2VHnuTkUZYfLy7hgV7NMBUJW2fu11P22EW3b9wziSGWPv9rRx/uYmwx/O4w svRg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:to:from:date; bh=A0tu9+47MHZHm+VZ3usPOYkjc7Jwj+afkj2ppineH4M=; b=zOEtS2paIGcimsRFyJ+iPARIZoJbubR4eJix6m/CuOrOu72xEcwLmHigDycU57mzk1 UNKT/dGixuqlhKIBGtOEdKuFPPaktuG/bIHluHpOKsGbdrWlT8dIwn1sPwYeIocANY5J SbeGfyNJKxe1ublWnSt0pciVY9p/L5kNquduAUEN3FC6t1VTgTCL0YAedLjFiFSXiRf6 PNqDlLDXyzWsbgxLGQiV49IAzTjK8onSAiFAVc6Z0SjEXYtd/TaYgDr0e/HYJ0AOyR8/ tNQmizo0yELOFTpRY1GYFyoG5ohDfpgO1vqDaUL9zqQG8BEEQ6+VPH2JRAZsQi+yB4gF gWng== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n2si16427244ilt.29.2021.09.21.04.19.16; Tue, 21 Sep 2021 04:19:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232229AbhIULT5 (ORCPT + 99 others); Tue, 21 Sep 2021 07:19:57 -0400 Received: from outbound-smtp33.blacknight.com ([81.17.249.66]:53731 "EHLO outbound-smtp33.blacknight.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232270AbhIULT5 (ORCPT ); Tue, 21 Sep 2021 07:19:57 -0400 Received: from mail.blacknight.com (pemlinmail01.blacknight.ie [81.17.254.10]) by outbound-smtp33.blacknight.com (Postfix) with ESMTPS id 93B4F16C008 for ; Tue, 21 Sep 2021 12:18:18 +0100 (IST) Received: (qmail 30926 invoked from network); 21 Sep 2021 11:18:18 -0000 Received: from unknown (HELO techsingularity.net) (mgorman@techsingularity.net@[84.203.17.29]) by 81.17.254.9 with ESMTPSA (AES256-SHA encrypted, authenticated); 21 Sep 2021 11:18:18 -0000 Date: Tue, 21 Sep 2021 12:18:17 +0100 From: Mel Gorman To: dsterba@suse.cz, Matthew Wilcox , Linux-MM , NeilBrown , Theodore Ts'o , Andreas Dilger , "Darrick J . Wong" , Michal Hocko , Dave Chinner , Rik van Riel , Vlastimil Babka , Johannes Weiner , Jonathan Corbet , Linux-fsdevel , LKML Subject: Re: [RFC PATCH 0/5] Remove dependency on congestion_wait in mm/ Message-ID: <20210921111816.GS3959@techsingularity.net> References: <20210920085436.20939-1-mgorman@techsingularity.net> <20210920125058.GI3959@techsingularity.net> <20210920141152.GM9286@twin.jikos.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20210920141152.GM9286@twin.jikos.cz> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 20, 2021 at 04:11:52PM +0200, David Sterba wrote: > On Mon, Sep 20, 2021 at 01:50:58PM +0100, Mel Gorman wrote: > > On Mon, Sep 20, 2021 at 12:42:44PM +0100, Matthew Wilcox wrote: > > > On Mon, Sep 20, 2021 at 09:54:31AM +0100, Mel Gorman wrote: > > > > This has been lightly tested only and the testing was useless as the > > > > relevant code was not executed. The workload configurations I had that > > > > used to trigger these corner cases no longer work (yey?) and I'll need > > > > to implement a new synthetic workload. If someone is aware of a realistic > > > > workload that forces reclaim activity to the point where reclaim stalls > > > > then kindly share the details. > > > > > > The stereeotypical "stalling on I/O" problem is to plug in one of the > > > crap USB drives you were given at a trade show and simply > > > dd if=/dev/zero of=/dev/sdb > > > sync > > > > > > > The test machines are 1500KM away so plugging in a USB stick but worst > > comes to the worst, I could test it on a laptop. > > There's a device mapper target dm-delay [1] that as it says delays the > reads and writes, so you could try to emulate the slow USB that way. > > [1] https://www.kernel.org/doc/html/latest/admin-guide/device-mapper/delay.html Ah, thanks for that tip. I wondered if something like this existed and clearly did not search hard enough. I was able to reproduce the problem without throttling but this could still be useful if examining cases where there are 2 or more BDIs with variable speeds. -- Mel Gorman SUSE Labs