Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8ED04C64EC4 for ; Wed, 8 Mar 2023 22:40:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229686AbjCHWkC (ORCPT ); Wed, 8 Mar 2023 17:40:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37612 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229513AbjCHWkA (ORCPT ); Wed, 8 Mar 2023 17:40:00 -0500 Received: from forward502c.mail.yandex.net (forward502c.mail.yandex.net [178.154.239.210]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A9CDE144B1 for ; Wed, 8 Mar 2023 14:39:58 -0800 (PST) Received: from sas2-ee8a69bedcfd.qloud-c.yandex.net (sas2-ee8a69bedcfd.qloud-c.yandex.net [IPv6:2a02:6b8:c14:252d:0:640:ee8a:69be]) by forward502c.mail.yandex.net (Yandex) with ESMTP id A5E6C5F425; Thu, 9 Mar 2023 01:39:56 +0300 (MSK) Received: by sas2-ee8a69bedcfd.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id qdlK4ADc3mI1-YobY5zlJ; Thu, 09 Mar 2023 01:39:55 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ya.ru; s=mail; t=1678315195; bh=jtp2l4lNFJPAxiRvDYywOQOC6WaE6pPy91DLgHdQQhI=; h=From:In-Reply-To:Cc:Date:References:To:Subject:Message-ID; b=AItsOs1tUQbS7iAuk2AT3NjB2XQBUNKQspE0WlDkhD+jJT1LG0nOLzhGV0oCoyS/A LOTbtus5nWHPWBaW0X3g7s+eLhJCCWUHcE6qAEU6NBRUkM1BZsYWCz/VmZLV9JwWSA a4xjilBcji57Mbv5zrKn1AeWxqphWGgIONs/6HjU= Authentication-Results: sas2-ee8a69bedcfd.qloud-c.yandex.net; dkim=pass header.i=@ya.ru Message-ID: Date: Thu, 9 Mar 2023 01:39:52 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v4 7/8] mm: vmscan: remove shrinker_rwsem from synchronize_shrinkers() Content-Language: en-US To: Qi Zheng , akpm@linux-foundation.org, hannes@cmpxchg.org, shakeelb@google.com, mhocko@kernel.org, roman.gushchin@linux.dev, muchun.song@linux.dev, david@redhat.com, shy828301@gmail.com, rppt@kernel.org Cc: sultan@kerneltoast.com, dave@stgolabs.net, penguin-kernel@I-love.SAKURA.ne.jp, paulmck@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org References: <20230307065605.58209-1-zhengqi.arch@bytedance.com> <20230307065605.58209-8-zhengqi.arch@bytedance.com> From: Kirill Tkhai In-Reply-To: <20230307065605.58209-8-zhengqi.arch@bytedance.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07.03.2023 09:56, Qi Zheng wrote: > Now there are no readers of shrinker_rwsem, so > synchronize_shrinkers() does not need to hold the > writer of shrinker_rwsem to wait for all running > shinkers to complete, synchronize_srcu() is enough. > > Signed-off-by: Qi Zheng > --- > mm/vmscan.c | 8 ++------ > 1 file changed, 2 insertions(+), 6 deletions(-) > > diff --git a/mm/vmscan.c b/mm/vmscan.c > index 7aaf6f94ac1b..ac7ab4aa344f 100644 > --- a/mm/vmscan.c > +++ b/mm/vmscan.c > @@ -796,15 +796,11 @@ EXPORT_SYMBOL(unregister_shrinker); > /** > * synchronize_shrinkers - Wait for all running shrinkers to complete. > * > - * This is equivalent to calling unregister_shrink() and register_shrinker(), > - * but atomically and with less overhead. This is useful to guarantee that all > - * shrinker invocations have seen an update, before freeing memory, similar to > - * rcu. > + * This is useful to guarantee that all shrinker invocations have seen an > + * update, before freeing memory. > */ > void synchronize_shrinkers(void) > { > - down_write(&shrinker_rwsem); > - up_write(&shrinker_rwsem); > atomic_inc(&shrinker_srcu_generation); > synchronize_srcu(&shrinker_srcu); > } Just curious, callers of synchronize_shrinkers() don't want to have parallel register_shrinker() and unregister_shrink() are completed? Here we only should wait for parallel shrink_slab(), correct?