All of lore.kernel.org
 help / color / mirror / Atom feed
From: baihaowen <baihaowen@meizu.com>
To: "yanteng si" <siyanteng01@gmail.com>, 司延腾 <siyanteng@loongson.cn>
Cc: "alexs@kernel.org" <alexs@kernel.org>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] docs/zh_CN: sync with original text Documentation/vm/page_owner.rst
Date: Mon, 18 Apr 2022 17:29:04 +0800	[thread overview]
Message-ID: <8b7485c9-eb17-e508-2d3e-a630fcaa998d@meizu.com> (raw)
In-Reply-To: <CAEensMx3qvL7qmT=PhxYoJ4v5P8USn1qyAGBcB1WR5R4FQ24og@mail.gmail.com>

在 4/18/22 9:58 AM, yanteng si 写道:
> yanteng si <siyanteng01@gmail.com> 于2022年4月15日周五 10:09写道:
>> 司延腾 <siyanteng@loongson.cn> 于2022年4月15日周五 09:31写道:
>>> Dear siyanteng
>>>
>>> Could you help to review my translation?
>>>
>>> Certainly!
>>>
>>> --CC siyanteng01@gmail.com
>>>
>>> Thanks,
>>> Yanteng
>>>
>>>
>>>
>>>
>>>
>>> -------- 原始邮件 --------
>>> 发件人:白浩文 <baihaowen@meizu.com>
>>> 时间:2022年4月12日 17:29
>>> 收件人:alexs@kernel.org,corbet@lwn.net
>>> 抄送:siyanteng@loongson.cn,白浩文 <baihaowen@meizu.com>,linux-doc@vger.kernel.org,linux-kernel@vger.kernel.org
>>> 主题:[PATCH V3] docs/zh_CN: sync with original text Documentation/vm/page_owner.rst
>>>
>>> As the tools/vm/page_owner_sort added some feature and original text
>>> updated, sync the translation of zh_CN.
>>>
>>> Signed-off-by: Haowen Bai <baihaowen@meizu.com>
>>> ---
>>> V1-&gt;V2: fix whitespace warning.
>>> V2-&gt;V3: fix some tab Alignment issue.
>>>
>>> Documentation/translations/zh_CN/vm/page_owner.rst | 54 +++++++++++++++++++++-
>>> 1 file changed, 53 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/translations/zh_CN/vm/page_owner.rst b/Documentation/translations/zh_CN/vm/page_owner.rst
>>> index 9e951fabba9d..0d4f94034db6 100644
>>> --- a/Documentation/translations/zh_CN/vm/page_owner.rst
>>> +++ b/Documentation/translations/zh_CN/vm/page_owner.rst
>>> @@ -103,14 +103,66 @@ page owner在默认情况下是禁用的。所以,如果你想使用它,你
>>> -m              按总内存排序
>>> -p              按pid排序。
>>> -P              按tgid排序。
>>> +               -n              按任务名称排序。
>>> -r              按内存释放时间排序。
>>> -s              按堆栈跟踪排序。
>>> -t              按时间排序(默认)。
>>> +               --sort <order>  指定排序顺序。排序语法是 [+|-]key[,[+|-]key[,...]]. 从
>>> +                                               **标准格式说明符**部分选择一个键。"+" 是可选的,因为默认方向是增加数字或字典顺序。
>>> +                                               允许混合使用缩写键和全称键。
>>> +
>>> +               Examples:
>>> +                               ./page_owner_sort <input> <output> --sort=n,+pid,-tgid
>>> +                               ./page_owner_sort <input> <output> --sort=at
>>>
>>> 其它函数:
>>>
>>> Cull:
>>> -               -c              通过比较堆栈跟踪而不是总块来进行剔除。
>>> +               --cull <rules>
>>> +                               指定筛选规则。筛选语法是 key[,key[,...]]。在**标准格式说明符**部分选择一个多字母键
>>> +
>>> +               <rules> 是逗号分隔列表形式的单个参数,它提供了一种指定单个筛选规则的方法。下面的**标准格式说明
>>> +                               符**部分描述了可识别的关键字。<rules> 可以由键 k1,k2, ... 顺序指定,如下面的
>>> +                               STANDARD SORT KEYS 部分所述。允许混合使用缩写形式和完整形式的键。
>>>
>>> +               Examples:
>>> +                               ./page_owner_sort <input> <output> --cull=stacktrace
>>> +                               ./page_owner_sort <input> <output> --cull=st,pid,name
>>> +                               ./page_owner_sort <input> <output> --cull=n,f
>>> Filter:
>>> -f              过滤掉内存已被释放的块的信息。
>>> +
>>> +       Select:
>>> +               --pid <pidlist>         通过 pid 进行选择。这将选择进程 ID 号出现在 <pidlist> 中的块。
>>> +               --tgid <tgidlist>       通过 tgid 进行选择。这将选择线程组 ID 号出现在 <tgidlist> 中的块。
>>> +               --name <cmdlist>        按任务名称选择。这将选择任务名称出现在 <cmdlist> 中的块。
>>> +
>>> +               <pidlist>、<tgidlist>、<cmdlist>是逗号分隔列表形式的单参数,它提供了一种指定单个选择规则的方法。
>>> +
>>> +
>>> +               Examples:
>>> +                               ./page_owner_sort <input> <output> --pid=1
>>> +                               ./page_owner_sort <input> <output> --tgid=1,2,3
>>> +                               ./page_owner_sort <input> <output> --name name1,name2
>>> +
>>> +       标准格式说明符
>>> +==========================
>> I ran a build test before reviewing and found the following ERROR:
>>
>> Sphinx parallel build error:
>> docutils.utils.SystemMessage: .../vm/page_owner.rst:149: (SEVERE/4)
>> Missing matching underline for section title overline.
>>
>> As for how to fix it, see:
>> <https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#bullet-lists>
>>
>> ref:: Documentation/translations/zh_CN/index.rst
>> 顺便说下,中文文档也需要遵守内核编码风格,风格中中文和英文的主要不同就是中文
>> 的字符标点占用两个英文字符宽度, 所以,当英文要求不要超过每行100个字符时,
>> 中文就不要超过50个字符。另外,也要注意'-','=' 等符号与相关标题的对齐。在将
>> 补丁提交到社区之前,一定要进行必要的checkpatch.pl检查和编译测试。
>>> _<
> Oops! I forgot to write Haowen's email address last week.
>
> So, --to baihaowen@meizu.com
>
> 标准格式说明符
> ==============
>
> In this way,It should fix this error. Then you need to pass the build
> test yourself. The general steps are as follows:
>
> $ cd xxxx/linux-next
> $ ./scripts/sphinx-pre-install
> $ . sphinx_2.4.4/bin/activate
> $ make cleandocs
> $ make htmldocs
>
> If  there is no error and warning about zh_CN/vm/page_owner.rst,
> Congratulations, passed!
> else
> Please try to fix them
>
> Thanks,
> Yanteng
>
>
>> Thanks,
>> Yanteng
>>
>>> +--sort 选项:
>>> +
>>> +       缩写键             全称键             描述
>>> +       p               pid             进程 ID
>>> +       tg              tgid            线程组 ID
>>> +       n               name            任务名称
>>> +       st              stacktrace      页面分配的调用栈
>>> +       T               txt             块的全文
>>> +       ft              free_ts         页面被释放的时间戳
>>> +       at              alloc_ts        页面分配的时间戳
>>> +
>>> +--curl 选项:
>>> +
>>> +       缩写键             全称键             描述
>>> +       p               pid             进程 ID
>>> +       tg              tgid            线程组 ID
>>> +       n               name            任务名称
>>> +       f               free            该页面是否已被释放
>>> +       st              stacktrace      页面分配的调用栈
>>> --
>>> 2.7.4
>>>
>>>
>>> </output></output></output></cmdlist></tgidlist></pidlist></cmdlist></cmdlist></tgidlist></tgidlist></pidlist></pidlist></output></output></output></rules></rules></rules></output></output></order></baihaowen@meizu.com></baihaowen@meizu.com></baihaowen@meizu.com>
>>>
>>> 本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件通知发件人并删除本邮件。
>>> This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it.
hi, yanteng
Thank you for your help and review.

-- 
Haowen Bai


  parent reply	other threads:[~2022-04-18  9:29 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15  1:30 [PATCH V3] docs/zh_CN: sync with original text Documentation/vm/page_owner.rst 司延腾
2022-04-15  2:09 ` yanteng si
2022-04-18  1:58   ` yanteng si
2022-04-18  9:28     ` [PATCH V4] " Haowen Bai
2022-04-18 12:41       ` Alex Shi
2022-04-19  1:23         ` Haowen Bai
2022-04-19  1:46           ` yanteng si
2022-04-19  2:07             ` [PATCH V5] " Haowen Bai
2022-04-19  2:33               ` yanteng si
2022-04-19  3:24                 ` baihaowen
2022-04-19  3:34                   ` [PATCH V6] " Haowen Bai
2022-04-19  4:27                   ` [PATCH V5] " Alex Shi
2022-04-19  5:49                     ` [PATCH V7] " Haowen Bai
2022-04-19  7:34                       ` [PATCH V8] " Haowen Bai
2022-04-19 14:42                         ` yanteng si
2022-04-20  3:06                           ` [PATCH 0/2] " Haowen Bai
2022-04-20  3:06                             ` [PATCH 1/2] docs/zh_CN: " Haowen Bai
2022-04-23 10:27                               ` Alex Shi
2022-04-24  2:56                                 ` baihaowen
2022-04-24  3:16                                   ` Alex Shi
2022-04-25  1:17                                     ` baihaowen
2022-04-25  3:19                                       ` yanteng si
2022-04-25  8:18                                         ` baihaowen
2022-04-26  6:57                                           ` yanteng si
2022-04-26  8:20                                       ` Alex Shi
2022-04-26  8:23                                         ` baihaowen
     [not found]                                           ` <3f93bb0d-5658-f269-f8cc-d0a964ffb68b@gmail.com>
2022-04-26  8:30                                             ` baihaowen
2022-04-20  3:06                             ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai
2022-04-20 12:31                               ` Bagas Sanjaya
2022-04-20 12:46                                 ` Jonathan Corbet
2022-04-24  3:38                               ` Akira Yokosawa
2022-04-24  5:24                                 ` Jonathan Corbet
2022-04-26  8:39                                 ` Alex Shi
2022-04-21 12:26                             ` [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst yanteng si
2022-04-22  1:40                               ` baihaowen
2022-04-22  2:35                                 ` Akira Yokosawa
2022-04-19  1:24         ` [PATCH V4] docs/zh_CN: " baihaowen
2022-04-18  9:29     ` baihaowen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-12  3:25 [PATCH] " Haowen Bai
2022-04-12  9:29 ` [PATCH V3] " Haowen Bai

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=8b7485c9-eb17-e508-2d3e-a630fcaa998d@meizu.com \
    --to=baihaowen@meizu.com \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=siyanteng01@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.