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 X-Spam-Level: X-Spam-Status: No, score=-6.4 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1606EC433B4 for ; Thu, 20 May 2021 08:56:18 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id C651E610CB for ; Thu, 20 May 2021 08:56:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C651E610CB Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 599528D000C; Thu, 20 May 2021 04:56:17 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 54AC88D0001; Thu, 20 May 2021 04:56:17 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3EB5B8D000C; Thu, 20 May 2021 04:56:17 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0238.hostedemail.com [216.40.44.238]) by kanga.kvack.org (Postfix) with ESMTP id 0DC948D0001 for ; Thu, 20 May 2021 04:56:17 -0400 (EDT) Received: from smtpin09.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id ABDA3B285 for ; Thu, 20 May 2021 08:56:16 +0000 (UTC) X-FDA: 78161002752.09.2DB2A75 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf24.hostedemail.com (Postfix) with ESMTP id B834AA0003A7 for ; Thu, 20 May 2021 08:56:14 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id 5C13861244; Thu, 20 May 2021 08:56:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1621500975; bh=sgLeXevKuKXA8xR8O04AMUkeyWmeIurWrzzxunkxA1g=; h=Date:From:To:Cc:Subject:From; b=ke+M4LKy8aSmeJ1xDFikIICVfCWakj24spM5nA40+D93teITJPCKICsDksvxrAbpM PcVToebo6TzMc/9juUVt6ud3b5RRptZQcxkz0ySOBNfhYB57QKs9EYkwh1J10ZCGwW uAsda28Qa0QQ49bEBcG9oiM8DWBEOylaybC43JpxEdv/KkJ1OxG6LSkc659FiH6+mt T+jYQaqN4U3Jp9Qdq6TCPZuRkK5y9TBV+f+FmJh4HwbsMUcXBLV45Qtv0Hd+HBH90g R0m4A4dp912tfN7VsU5NOpvnOcLSzKPGMtRhunCfsTAcu+uxUMuIahFcAd7UBBWliK j4aJARyTvw3Qw== Date: Thu, 20 May 2021 11:56:09 +0300 From: Mike Rapoport To: lsf-pc@lists.linux-foundation.org Cc: linux-mm@kvack.org Subject: [LSF/MM TOPIC] mm documentation Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: B834AA0003A7 Authentication-Results: imf24.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=ke+M4LKy; dmarc=pass (policy=none) header.from=kernel.org; spf=pass (imf24.hostedemail.com: domain of rppt@kernel.org designates 198.145.29.99 as permitted sender) smtp.mailfrom=rppt@kernel.org X-Rspamd-Server: rspam03 X-Stat-Signature: scr45wzokqspkpq5x4e747wskrrus96s X-HE-Tag: 1621500974-723930 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: Hi, The mm documentation is, well, not entirely up to date. We can opt for dropping the outdated parts, which would generate a nice negative diffstat, but identifying the outdated documentation requires nearly as much effort as updating it, so I think that making and keeping the docs up to date would be a better option. I'd like to discuss what can be done process-wise to improve the situation. Some points I had in mind: * Pay more attention to docs during review * Set an expectation level for docs accompanying a changeset * Spend some cycles to review and update the existing docs * Spend some more cycles to add new documentation * Participate in prorams like Google Season of Docs I'd appreciate a discussion about how we can improve the existing memory management documentation so that a reader can get a coherent view of it, what are the gaps (although they are too many), and what would be the best way to close these gaps. -- Sincerely yours, Mike.