Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1713440pxb; Fri, 22 Oct 2021 06:20:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy8TDb2ZBl+trokUjzTO8IrJVh+HXyd0uSKjDsqHhlbsxMBIjdZsMakae+oy6R9v/FEfD58 X-Received: by 2002:a17:906:b06:: with SMTP id u6mr7694892ejg.330.1634908820030; Fri, 22 Oct 2021 06:20:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634908820; cv=none; d=google.com; s=arc-20160816; b=THvFHs8CyGqgw36jA3V112waMCf8E4XhrFdqTZcKbiaGs3jLwtrfqPGNEFsBOS6MB3 zzfzPyPj5jqu7qZIZcaiWX1NcAGJyNbHwq064Yxooe/N5Xs3lvjr4cIU5L3R+eq/XlL5 FZhqakoqxQf0K/wRwVW1XABbMKQQpzEQElvAv8etUQBKo65R3lIT/C2ImPVnHfLQlcTa K17yjYzNqbEcS0OGJcdtiEbhiKNvjmre5UEyiCSiLcYd53OQsUPGYJY6xNyJq+14cg+4 DlLw/Rs55rhEGUuPE6gv/WHfzrOla1Mmrpr22h/DryYATjqxBpVAvjp3jbat+OAF5sw5 svfg== 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:cc:to:from:date; bh=g9VykZu6pqwzECc2yI2QJ2EHSiU1f4gz2cjIwmHGmAs=; b=H4/rAuxQI0ubcLw/jGJZNxp+AvYbrkHnyvVe3kw0+SRd9Y86ap4YC/nqNIbX99mLtz MYZehXYXQ6KyWPljRwi5SrPJtquEOhuO1Akw8uOkosVsMLAEDaRhUnwdjI4zfpg1qYX1 6yYyTk9ZwtwPy88lySXcqa3PkXpPrAjlNvIzB90A9bBi56cAzzr5C31roBMfIMygFtlP 2k3zT8RIiEL7fyuPKiBRsJjjO8ro4Uww749EWTO3kdfB0T50FmuYnb/7Ky6odAn+58Ql X4JoPt+UB7d7TablkJtyJz8ScIQtR3VdRdNa2bauCOxD/4QT4N9QO1oGHQeyctKwhT9T d0+w== 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 d5si10245433eje.143.2021.10.22.06.19.54; Fri, 22 Oct 2021 06:20:20 -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 S232292AbhJVNTz (ORCPT + 99 others); Fri, 22 Oct 2021 09:19:55 -0400 Received: from outbound-smtp29.blacknight.com ([81.17.249.32]:47418 "EHLO outbound-smtp29.blacknight.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230342AbhJVNTw (ORCPT ); Fri, 22 Oct 2021 09:19:52 -0400 Received: from mail.blacknight.com (pemlinmail01.blacknight.ie [81.17.254.10]) by outbound-smtp29.blacknight.com (Postfix) with ESMTPS id 456C018E11B for ; Fri, 22 Oct 2021 14:17:34 +0100 (IST) Received: (qmail 6329 invoked from network); 22 Oct 2021 13:17:34 -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); 22 Oct 2021 13:17:34 -0000 Date: Fri, 22 Oct 2021 14:17:32 +0100 From: Mel Gorman To: NeilBrown Cc: Andrew Morton , Theodore Ts'o , Andreas Dilger , "Darrick J . Wong" , Matthew Wilcox , Michal Hocko , Dave Chinner , Rik van Riel , Vlastimil Babka , Johannes Weiner , Jonathan Corbet , Linux-MM , Linux-fsdevel , LKML Subject: Re: [PATCH v4 0/8] Remove dependency on congestion_wait in mm/ Message-ID: <20211022131732.GK3959@techsingularity.net> References: <20211019090108.25501-1-mgorman@techsingularity.net> <163486531001.17149.13533181049212473096@noble.neil.brown.name> <20211022083927.GI3959@techsingularity.net> <163490199006.17149.17259708448207042563@noble.neil.brown.name> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <163490199006.17149.17259708448207042563@noble.neil.brown.name> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 22, 2021 at 10:26:30PM +1100, NeilBrown wrote: > On Fri, 22 Oct 2021, Mel Gorman wrote: > > On Fri, Oct 22, 2021 at 12:15:10PM +1100, NeilBrown wrote: > > > > > In general, I still don't like the use of wake_up_all(), though it won't > > > cause incorrect behaviour. > > > > > > > Removing wake_up_all would be tricky. > > I think there is a misunderstanding. Removing wake_up_all() is as > simple as > s/wake_up_all/wake_up/ > > If you used prepare_to_wait_exclusive(), then wake_up() would only wake > one waiter, while wake_up_all() would wake all of them. > As you use prepare_to_wait(), wake_up() will wake all waiters - as will > wake_up_all(). > Ok, yes, there was a misunderstanding. I thought you were suggesting a move to exclusive wakeups. I felt that the wake_up_all was explicit in terms of intent and that I really meant for all tasks to wake instead of one at a time. -- Mel Gorman SUSE Labs