From: Alex Shi <seakeel@gmail.com>
To: Dongliang Mu <dzm91@hust.edu.cn>,
si.yanteng@linux.dev, alexs@kernel.org, corbet@lwn.net,
Yanteng Si <siyanteng@loongson.cn>
Cc: hust-os-kernel-patches@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] docs/zh_CN: update the translation of mm/admon/faq.rst
Date: Tue, 22 Oct 2024 09:43:50 +0800 [thread overview]
Message-ID: <25a18538-0704-436c-8df7-a485e644496b@gmail.com> (raw)
In-Reply-To: <20e7e17b18542ecbf924234ed40438b95345e514.1729327831.git.dzm91@hust.edu.cn>
Reviewed-by: Alex Shi <alexs@kernel.org>
On 10/19/24 16:54, Dongliang Mu wrote:
> Update to commit c6bb975aa60b ("Docs/mm/damon/faq: remove old questions")
>
> scripts/checktransupdate.py reports:
>
> Documentation/translations/zh_CN/mm/damon/faq.rst
> commit c6bb975aa60b ("Docs/mm/damon/faq: remove old questions")
> 1 commits needs resolving in total
>
> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
> ---
> .../translations/zh_CN/mm/damon/faq.rst | 17 -----------------
> 1 file changed, 17 deletions(-)
>
> diff --git a/Documentation/translations/zh_CN/mm/damon/faq.rst b/Documentation/translations/zh_CN/mm/damon/faq.rst
> index de4be417494a..234d63f4f072 100644
> --- a/Documentation/translations/zh_CN/mm/damon/faq.rst
> +++ b/Documentation/translations/zh_CN/mm/damon/faq.rst
> @@ -13,23 +13,6 @@
> 常见问题
> ========
>
> -为什么是一个新的子系统,而不是扩展perf或其他用户空间工具?
> -==========================================================
> -
> -首先,因为它需要尽可能的轻量级,以便可以在线使用,所以应该避免任何不必要的开销,如内核-用户
> -空间的上下文切换成本。第二,DAMON的目标是被包括内核在内的其他程序所使用。因此,对特定工具
> -(如perf)的依赖性是不可取的。这就是DAMON在内核空间实现的两个最大的原因。
> -
> -
> -“闲置页面跟踪” 或 “perf mem” 可以替代DAMON吗?
> -==============================================
> -
> -闲置页跟踪是物理地址空间访问检查的一个低层次的原始方法。“perf mem”也是类似的,尽管它可以
> -使用采样来减少开销。另一方面,DAMON是一个更高层次的框架,用于监控各种地址空间。它专注于内
> -存管理优化,并提供复杂的精度/开销处理机制。因此,“空闲页面跟踪” 和 “perf mem” 可以提供
> -DAMON输出的一个子集,但不能替代DAMON。
> -
> -
> DAMON是否只支持虚拟内存?
> =========================
>
next prev parent reply other threads:[~2024-10-22 1:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1729327831.git.dzm91@hust.edu.cn>
2024-10-19 8:54 ` [PATCH 1/6] docs/zh_CN: update the translation of mm/hmm.rst Dongliang Mu
2024-10-22 1:43 ` Alex Shi
2024-10-22 2:02 ` Alex Shi
2024-10-22 3:28 ` Alex Shi
2024-10-19 8:54 ` [PATCH 2/6] docs/zh_CN: update the translation of mm/active_mm.rst Dongliang Mu
2024-10-22 1:43 ` Alex Shi
2024-10-19 8:54 ` [PATCH 3/6] docs/zh_CN: update the translation of mm/admon/faq.rst Dongliang Mu
2024-10-22 1:43 ` Alex Shi [this message]
2024-10-19 8:54 ` [PATCH 4/6] docs/zh_CN: update the translation of mm/overcommit-accounting.rst Dongliang Mu
2024-10-22 1:44 ` Alex Shi
2024-10-19 8:54 ` [PATCH 5/6] docs/zh_CN: update the translation of mm/page_table_check.rst Dongliang Mu
2024-10-22 1:44 ` Alex Shi
2024-10-19 8:54 ` [PATCH 6/6] docs/zh_CN: update the translation of mm/page_owner.rst Dongliang Mu
2024-10-22 1:44 ` Alex Shi
2024-10-24 21:45 ` [PATCH 0/6] update the translation of partial files in mm Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25a18538-0704-436c-8df7-a485e644496b@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--cc=siyanteng@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®