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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5C4D3C433F5 for ; Tue, 19 Apr 2022 17:58:42 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E1A836B0072; Tue, 19 Apr 2022 13:58:41 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id D55036B0073; Tue, 19 Apr 2022 13:58:41 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id BF5966B0074; Tue, 19 Apr 2022 13:58:41 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.a.hostedemail.com [64.99.140.24]) by kanga.kvack.org (Postfix) with ESMTP id B1E8B6B0072 for ; Tue, 19 Apr 2022 13:58:41 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay13.hostedemail.com (Postfix) with ESMTP id 866486245E for ; Tue, 19 Apr 2022 17:58:41 +0000 (UTC) X-FDA: 79374388842.11.82F168E Received: from out1.migadu.com (out1.migadu.com [91.121.223.63]) by imf26.hostedemail.com (Postfix) with ESMTP id A7FE514000B for ; Tue, 19 Apr 2022 17:58:39 +0000 (UTC) Date: Tue, 19 Apr 2022 10:58:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1650391118; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=LwMEsoXiVBDMMlTnWr1tF9A5/2DsUEfBfNSdTUYTpLQ=; b=GSeP4KlZhPpf+uMxHvjav5FPXp0dJ579TdtR8KLfaXlePkdpBE1fC+WWHOtb/f2Y2ujT0C wGB6njWc6l5pB8jXYw9Nrrp5C0Rgiq2pRexIanJAIBeZm7haDbH/jW8fuz7j7gtkze/8yP JULqwDoS/c8b/+WlglVpvr6YOWVyYJU= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Roman Gushchin To: Mike Rapoport Cc: linux-mm@kvack.org, Andrew Morton , Dave Chinner , linux-kernel@vger.kernel.org, Johannes Weiner , Michal Hocko , Shakeel Butt , Yang Shi Subject: Re: [PATCH rfc 0/5] mm: introduce shrinker sysfs interface Message-ID: References: <20220416002756.4087977-1-roman.gushchin@linux.dev> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: linux.dev X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: A7FE514000B X-Stat-Signature: ja3zaq5zkybu6mc9qzu675rmjhau3ff6 Authentication-Results: imf26.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=GSeP4KlZ; spf=pass (imf26.hostedemail.com: domain of roman.gushchin@linux.dev designates 91.121.223.63 as permitted sender) smtp.mailfrom=roman.gushchin@linux.dev; dmarc=pass (policy=none) header.from=linux.dev X-Rspam-User: X-HE-Tag: 1650391119-839814 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, Apr 19, 2022 at 09:33:48AM +0300, Mike Rapoport wrote: > On Mon, Apr 18, 2022 at 10:27:34AM -0700, Roman Gushchin wrote: > > On Mon, Apr 18, 2022 at 12:27:36PM +0300, Mike Rapoport wrote: > > > On Fri, Apr 15, 2022 at 05:27:51PM -0700, Roman Gushchin wrote: > > > > There are 50+ different shrinkers in the kernel, many with their own bells and > > > > whistles. Under the memory pressure the kernel applies some pressure on each of > > > > them in the order of which they were created/registered in the system. Some > > > > of them can contain only few objects, some can be quite large. Some can be > > > > effective at reclaiming memory, some not. > > > > > > > > The only existing debugging mechanism is a couple of tracepoints in > > > > do_shrink_slab(): mm_shrink_slab_start and mm_shrink_slab_end. They aren't > > > > covering everything though: shrinkers which report 0 objects will never show up, > > > > there is no support for memcg-aware shrinkers. Shrinkers are identified by their > > > > scan function, which is not always enough (e.g. hard to guess which super > > > > block's shrinker it is having only "super_cache_scan"). They are a passive > > > > mechanism: there is no way to call into counting and scanning of an individual > > > > shrinker and profile it. > > > > > > > > To provide a better visibility and debug options for memory shrinkers > > > > this patchset introduces a /sys/kernel/shrinker interface, to some extent > > > > similar to /sys/kernel/slab. > > > > > > Wouldn't debugfs better fit the purpose of shrinker debugging? > > > > I think sysfs fits better, but not a very strong opinion. > > > > Even though the interface is likely not very useful for the general > > public, big cloud instances might wanna enable it to gather statistics > > (and it's certainly what we gonna do at Facebook) and to provide > > additional data when something is off. They might not have debugfs > > mounted. And it's really similar to /sys/kernel/slab. > > And there is also similar /proc/vmallocinfo so why not /proc/shrinker? ;-) > > I suspect slab ended up in sysfs because nobody suggested to use debugfs > back then. I've been able to track the transition from /proc/slabinfo to > /proc/slubinfo to /sys/kernel/slab, but could not find why Christoph chose > sysfs in the end. > > > Are there any reasons why debugfs is preferable? > > debugfs is more flexible because it's not stable kernel ABI so if there > will be need/desire to change the layout and content of the files with > debugfs it can be done more easily. > > Is this a real problem for Facebook to mount debugfs? ;-) Fair enough, switching to debugfs in the next version. Thanks!