mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pengyu Zhang <zpenya1314@gmail.com>
To: alexs@kernel.org, siyanteng@loongson.cn, corbet@lwn.net,
	seakeel@gmail.com, si.yanteng@linux.dev
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	zpenya1314@gmail.com, yaxin_wang_uestc@163.com,
	zenghui.yu@linux.dev
Subject: Re: [PATCH v5 1/3] Docs/zh_CN: Translate page_tables.rst to Simplified Chinese
Date: Tue, 15 Oct 2024 23:43:01 +0800	[thread overview]
Message-ID: <20241015154301.4736-1-zpenya1314@gmail.com> (raw)

Hi Yanteng

>> +随着内存容量的增加,久而久之层级结构逐渐加深。Linux 最初使用 4KB 页面和一个名为
>> +`swapper_pg_dir` 的页表,该页表拥有 1024 个条目(entries),覆盖 4MB 的内存,
>> +事实上Torvald 的第一台计算机正好就有 4MB 物理内存。条目在这张表中被称为 *PTE*:s
>> +- 页表条目(page table entries)。
>
>page table entries -> 页表项。 So:
>每一个页表项在这张表中被称为 *PTE*:s
>
>> +
>> +软件页表层级结构反映了页表硬件已经变得分层化的事实,而这种分层化的目的是为了节省
>> +页表内存并加快地址映射速度。
>> +
>> +当然,人们可以想象一张拥有大量条目的单一线性的页表将整个内存分为一个个页。而且,
>Hmm, let's exec %s/条目/页表项 in vim.

This translation is indeed the most confusing part for me. When 'entry' appears
on its own, I previously tended to translate it as '表项'.  However, I noticed
that other Chinese documents have used '条目', so I reused their translation.
In our context, though, I believe 'page table entries' and 'entry' are better
translated as'页表项' and '表项' respectively.

How about exec s/页表条目/页表项 and s/条目/表项.

Thanks,
Pengyu

             reply	other threads:[~2024-10-15 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 15:43 Pengyu Zhang [this message]
2024-10-16  2:43 ` Yanteng Si
  -- strict thread matches above, loose matches on Subject: below --
2024-10-14 15:55 [PATCH v5 0/3] Translate page_tables.rst and fix PFN calculation Pengyu Zhang
2024-10-14 15:55 ` [PATCH v5 1/3] Docs/zh_CN: Translate page_tables.rst to Simplified Chinese Pengyu Zhang
2024-10-15  2:23   ` Yanteng Si

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=20241015154301.4736-1-zpenya1314@gmail.com \
    --to=zpenya1314@gmail.com \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seakeel@gmail.com \
    --cc=si.yanteng@linux.dev \
    --cc=siyanteng@loongson.cn \
    --cc=yaxin_wang_uestc@163.com \
    --cc=zenghui.yu@linux.dev \
    /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®