From mboxrd@z Thu Jan 1 00:00:00 1970 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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 29AFCC433EF for ; Mon, 27 Sep 2021 16:54:17 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id BBBE260F58 for ; Mon, 27 Sep 2021 16:54:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org BBBE260F58 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kerneltoast.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id 4A890900003; Mon, 27 Sep 2021 12:54:16 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 45728900002; Mon, 27 Sep 2021 12:54:16 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 2F83E900003; Mon, 27 Sep 2021 12:54:16 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0220.hostedemail.com [216.40.44.220]) by kanga.kvack.org (Postfix) with ESMTP id 1C435900002 for ; Mon, 27 Sep 2021 12:54:16 -0400 (EDT) Received: from smtpin01.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id AA5AE82499A8 for ; Mon, 27 Sep 2021 16:54:15 +0000 (UTC) X-FDA: 78633951270.01.E97F7B8 Received: from mail-pl1-f172.google.com (mail-pl1-f172.google.com [209.85.214.172]) by imf20.hostedemail.com (Postfix) with ESMTP id 5B79AD0000B0 for ; Mon, 27 Sep 2021 16:54:15 +0000 (UTC) Received: by mail-pl1-f172.google.com with SMTP id y1so12170950plk.10 for ; Mon, 27 Sep 2021 09:54:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=LzV6OOmZa/qvBdae7Jcnof6iK8r853c6tPcY+9ZAt6o=; b=eWksj66uZswj8lxU1fDSybmDNils3dvtPTiDux4fIUtfw5WNU7QQVxvnid2l1Uvi/8 6hEh89hnkCS0N+MJ+1BjNMMleukMtHJpCA0tEQMuWkOybf289nU3UrvoKDee9fueYHbb wYq+280y2KUknpwAMnTR6omdhI2oabXhW3KixOr0xnGj+ad35n4NzfKBfGdoDTVtjvGD NHLf30tYI1Wlh576+fmjB6DFjdd6a4NCFoy1To0Oj88eOc+6wwRLMu0fVBpuU1Obh0Fr haA/y7ewOmdgEy0rWPTUKurk53+WmVmqfNOg7febJE/3wxnk91ufnApwjKAGZPZ1V5Os LXSA== X-Gm-Message-State: AOAM5310Pz60mMtnvfPFyhBvN/dwNEf4HNtlP8AFHK7bQQ2wOdK4GyQt QlYQs2d3kZepL72rVs5CcBpWpHMdTkE= X-Google-Smtp-Source: ABdhPJw5w+ElVIJ+JGw99m6Ms/0MuX0gHwyQ419Kpo+mWLmE05v5KETYWHqu3MXb1mkhuQozak8+4A== X-Received: by 2002:a17:90b:4b06:: with SMTP id lx6mr99940pjb.160.1632761642247; Mon, 27 Sep 2021 09:54:02 -0700 (PDT) Received: from sultan-box.localdomain ([204.152.215.247]) by smtp.gmail.com with ESMTPSA id r7sm17568873pff.112.2021.09.27.09.54.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Sep 2021 09:54:01 -0700 (PDT) Date: Mon, 27 Sep 2021 09:53:59 -0700 From: Sultan Alsawaf To: Michal Hocko Cc: Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm: vmscan: Replace shrinker_rwsem trylocks with SRCU protection Message-ID: References: <20210927074823.5825-1-sultan@kerneltoast.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Server: rspam02 X-Rspamd-Queue-Id: 5B79AD0000B0 X-Stat-Signature: 36ikbfmh1f87oh4wcbjxbmqw3348bye5 Authentication-Results: imf20.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf20.hostedemail.com: domain of sultan.kerneltoast@gmail.com designates 209.85.214.172 as permitted sender) smtp.mailfrom=sultan.kerneltoast@gmail.com X-HE-Tag: 1632761655-274278 X-Bogosity: Ham, tests=bogofilter, spamicity=0.022603, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, Sep 27, 2021 at 10:36:36AM +0200, Michal Hocko wrote: > Can you be more specific about those scenarios please? I see frequent tmpfs mounts/unmounts in Android which result in lots of superblocks being created and destroyed, and each superblock has its own shrinker. > I have a vague recollection that this approach has been proposed in the > past. Have you checked previous attempts? I wasn't aware that there were previous attempts. Is this [1] the previous attempt you're thinking of? It seems like the thread just died out. Was the main gripe that always enabling CONFIG_SRCU increased the kernel's size too much when tinyfication was desired? Sultan [1] https://lore.kernel.org/all/153365347929.19074.12509495712735843805.stgit@localhost.localdomain/