From patchwork Wed Feb 1 09:41:54 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Mike Rapoport X-Patchwork-Id: 51256 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:eb09:0:0:0:0:0 with SMTP id s9csp181104wrn; Wed, 1 Feb 2023 01:51:50 -0800 (PST) X-Google-Smtp-Source: AK7set+JCzf6aqtJx8uRilEnzJ1TcrYRuobqpiBcHEv3u30FogMVM7WjDp+K6zGiswUuCu5yr476 X-Received: by 2002:a17:906:cf83:b0:887:6c23:193f with SMTP id um3-20020a170906cf8300b008876c23193fmr1491074ejb.44.1675245110131; Wed, 01 Feb 2023 01:51:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1675245110; cv=none; d=google.com; s=arc-20160816; b=wuoTOBrEQc2AwYDoHSPBRZPiw5z7OJ8Wy9EIw+7xa3JvpnNKXRZoaqPAqBjwEkdgiH 8BlvpZYLEcNMYSf705usAVv5fsiqdvgw3qG75tw3rEs4+sLj/1Tf8wDLzQaiEQjU/V31 1ujH3FS71rBfk1pIiEr43j3o0wkMO8/EwTnfpz69HK39PaLSz9dmt3lbohOGbfucYWMg c6AfCBIhpU1+vOyCvS9qGQohGbpSVeKIlfQC5WLAIH2zGQpk9xaJmU+hb+5TdIT/wbuz ul3GX3uL0pBxK+//czpHMybmXZyzOiznfanwMXNNAv/q0BZWCJ4hHOicurOyYejFxQuq meVA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=uGi+V5Y0nOKjcxn+/znr6RnDWyBMfcwg8vWx4XSQ4Bg=; b=vvtA7a5qr7/uKmq/9GVdAbwU2enNhlmBHKdZg6Ta9OlSxNptzwGhnt0kqDqGRTpQ7F 2FnGypsVjp80V6idsjkIcnnPrp+pM/Wool3EcQQP1lYPuNnvA/beN+s5fsQD/NCAijgT xCwFnbyG8PvZiys5EhfTU0BJ74pQd7AksPYTmR7fet0g5L5mdWRJclTgl5GObkfgYzPh EpoTQTzEtAIoR8Hirk7uLY6UfBOFD4nMufQlTsZbPiS4qnwAnnTrYztM0akWan+Rnymc wX3BwjSfEaS4RrXnHMVsPtklAQooH9RfYZpHxGXZhFN3MncOtuWaj9dIaAkjVlAVt8CX hqQw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=LbRn4123; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id uk39-20020a170907ca2700b0084cbde35b49si19583309ejc.990.2023.02.01.01.51.26; Wed, 01 Feb 2023 01:51:50 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=LbRn4123; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232139AbjBAJmV (ORCPT + 99 others); Wed, 1 Feb 2023 04:42:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58352 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232132AbjBAJmP (ORCPT ); Wed, 1 Feb 2023 04:42:15 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0CF635EFA1; Wed, 1 Feb 2023 01:42:13 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 524BDB82153; Wed, 1 Feb 2023 09:42:12 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3D8B1C433D2; Wed, 1 Feb 2023 09:42:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1675244531; bh=fyLlrQ6ozpspF/7rhlxFsw35A1aS+p/JI5vd/nqAEI8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=LbRn4123EqJwl5vEXwKvzNGH6riD3I4I8aAz+Bht3IeAsN9v/FQtOQDySY6xwCW++ J76LeDvdGxFuaiZI9wS25/zn4SS2p0HRbPitWmdPEf7QCh4zpPuox6WOWZZNE8MAEG ag74tfu35YPsO/TUR6hAYEIUVlIUkHesj/LPxDwImyWSiy7jAlrFbabrvfOZ0W2aes bxWMOBNUvVA/pSsFPwogytySjjvjzHMDwUvJvUrFq2iGo+AEzRiCLXU00FQ0l4uUJi LOHLmsZvU91nMYrqatg0Zc0qb4E+8bjgiklJOM74gBjaaax7PJjQA42qdcNDmxyobq Gh6fhOMgdbaNg== From: Mike Rapoport To: Jonathan Corbet Cc: Bagas Sanjaya , Mike Rapoport , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: [PATCH v3 1/3] docs/mm: Physical Memory: remove useless markup Date: Wed, 1 Feb 2023 11:41:54 +0200 Message-Id: <20230201094156.991542-2-rppt@kernel.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20230201094156.991542-1-rppt@kernel.org> References: <20230201094156.991542-1-rppt@kernel.org> MIME-Version: 1.0 X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1756621816328040303?= X-GMAIL-MSGID: =?utf-8?q?1756621816328040303?= From: "Mike Rapoport (IBM)" Jon says: > +See also :ref:`Page Reclaim `. Can also just be "See also Documentation/mm/page_reclaim.rst". The right things will happen in the HTML output, readers of the plain-text will know immediately where to go, and we don't have to add the label clutter. Remove reference markup and unnecessary labes and use plain file names. Fixes: 5d8c5e430a63 ("docs/mm: Physical Memory: add structure, introduction and nodes description") Suggested-by: Jonathan Corbet Acked-by: Bagas Sanjaya Signed-off-by: Mike Rapoport (IBM) --- Documentation/core-api/dma-api.rst | 2 -- Documentation/mm/page_reclaim.rst | 2 -- Documentation/mm/physical_memory.rst | 12 ++++++------ 3 files changed, 6 insertions(+), 10 deletions(-) diff --git a/Documentation/core-api/dma-api.rst b/Documentation/core-api/dma-api.rst index c847a5b0a0d3..829f20a193ca 100644 --- a/Documentation/core-api/dma-api.rst +++ b/Documentation/core-api/dma-api.rst @@ -1,5 +1,3 @@ -.. _dma_api: - ============================================ Dynamic DMA mapping using the generic device ============================================ diff --git a/Documentation/mm/page_reclaim.rst b/Documentation/mm/page_reclaim.rst index 3fccde066436..50a30b7f8ac3 100644 --- a/Documentation/mm/page_reclaim.rst +++ b/Documentation/mm/page_reclaim.rst @@ -1,7 +1,5 @@ .. SPDX-License-Identifier: GPL-2.0 -.. _page_reclaim: - ============ Page Reclaim ============ diff --git a/Documentation/mm/physical_memory.rst b/Documentation/mm/physical_memory.rst index d24220d62475..3f3c02aa6e6e 100644 --- a/Documentation/mm/physical_memory.rst +++ b/Documentation/mm/physical_memory.rst @@ -39,8 +39,8 @@ one of the types described below. * ``ZONE_DMA`` and ``ZONE_DMA32`` historically represented memory suitable for DMA by peripheral devices that cannot access all of the addressable memory. For many years there are better more and robust interfaces to get - memory with DMA specific requirements (:ref:`DMA API `), but - ``ZONE_DMA`` and ``ZONE_DMA32`` still represent memory ranges that have + memory with DMA specific requirements (Documentation/core-api/dma-api.rst), + but ``ZONE_DMA`` and ``ZONE_DMA32`` still represent memory ranges that have restrictions on how they can be accessed. Depending on the architecture, either of these zone types or even they both can be disabled at build time using ``CONFIG_ZONE_DMA`` and @@ -64,9 +64,9 @@ one of the types described below. change, their content may move between different physical pages. Often ``ZONE_MOVABLE`` is populated during memory hotplug, but it may be also populated on boot using one of ``kernelcore``, ``movablecore`` and - ``movable_node`` kernel command line parameters. See :ref:`Page migration - ` and :ref:`Memory Hot(Un)Plug ` - for additional details. + ``movable_node`` kernel command line parameters. See + Documentation/mm/page_migration.rst and + Documentation/admin-guide/mm/memory_hotplug.rst for additional details. * ``ZONE_DEVICE`` represents memory residing on devices such as PMEM and GPU. It has different characteristics than RAM zone types and it exists to provide @@ -252,7 +252,7 @@ General Reclaim control ~~~~~~~~~~~~~~~ -See also :ref:`Page Reclaim `. +See also Documentation/mm/page_reclaim.rst. ``kswapd`` Per-node instance of kswapd kernel thread.