mirror of
https://github.com/torvalds/linux.git
synced 2026-05-26 08:02:27 +02:00
Merge branch 'docs-mw' into docs-next
This commit is contained in:
commit
df39f6bb3c
|
|
@ -59,7 +59,7 @@ differences.
|
|||
* JFFS2 is a write-through file-system, while UBIFS supports write-back,
|
||||
which makes UBIFS much faster on writes.
|
||||
|
||||
Similarly to JFFS2, UBIFS supports on-the-flight compression which makes
|
||||
Similarly to JFFS2, UBIFS supports on-the-fly compression which makes
|
||||
it possible to fit quite a lot of data to the flash.
|
||||
|
||||
Similarly to JFFS2, UBIFS is tolerant of unclean reboots and power-cuts.
|
||||
|
|
|
|||
|
|
@ -38,22 +38,10 @@ not affect to allocation performance, especially if the static keys jump
|
|||
label patching functionality is available. Following is the kernel's code
|
||||
size change due to this facility.
|
||||
|
||||
- Without page owner::
|
||||
|
||||
text data bss dec hex filename
|
||||
48392 2333 644 51369 c8a9 mm/page_alloc.o
|
||||
|
||||
- With page owner::
|
||||
|
||||
text data bss dec hex filename
|
||||
48800 2445 644 51889 cab1 mm/page_alloc.o
|
||||
6662 108 29 6799 1a8f mm/page_owner.o
|
||||
1025 8 8 1041 411 mm/page_ext.o
|
||||
|
||||
Although, roughly, 8 KB code is added in total, page_alloc.o increase by
|
||||
520 bytes and less than half of it is in hotpath. Building the kernel with
|
||||
page owner and turning it on if needed would be great option to debug
|
||||
kernel memory problem.
|
||||
Although enabling page owner increases kernel size by several kilobytes,
|
||||
most of this code is outside page allocator and its hot path. Building
|
||||
the kernel with page owner and turning it on if needed would be great
|
||||
option to debug kernel memory problem.
|
||||
|
||||
There is one notice that is caused by implementation detail. page owner
|
||||
stores information into the memory from struct page extension. This memory
|
||||
|
|
|
|||
|
|
@ -379,7 +379,7 @@ to subscribe and unsubscribe from the list can be found at:
|
|||
There are archives of the mailing list on the web in many different
|
||||
places. Use a search engine to find these archives. For example:
|
||||
|
||||
http://dir.gmane.org/gmane.linux.kernel
|
||||
https://lore.kernel.org/lkml/
|
||||
|
||||
It is highly recommended that you search the archives about the topic
|
||||
you want to bring up, before you post it to the list. A lot of things
|
||||
|
|
|
|||
|
|
@ -564,7 +564,7 @@ of ftrace. Here is a list of some of the key files:
|
|||
|
||||
start::
|
||||
|
||||
trace_fd = open("trace_marker", WR_ONLY);
|
||||
trace_fd = open("trace_marker", O_WRONLY);
|
||||
|
||||
Note: Writing into the trace_marker file can also initiate triggers
|
||||
that are written into /sys/kernel/tracing/events/ftrace/print/trigger
|
||||
|
|
|
|||
|
|
@ -394,7 +394,7 @@ trovati al sito:
|
|||
Ci sono diversi archivi della lista di discussione. Usate un qualsiasi motore
|
||||
di ricerca per trovarli. Per esempio:
|
||||
|
||||
http://dir.gmane.org/gmane.linux.kernel
|
||||
https://lore.kernel.org/lkml/
|
||||
|
||||
É caldamente consigliata una ricerca in questi archivi sul tema che volete
|
||||
sollevare, prima di pubblicarlo sulla lista. Molte cose sono già state
|
||||
|
|
|
|||
|
|
@ -410,7 +410,7 @@ https://bugzilla.kernel.org に行ってください。もし今後のバグレ
|
|||
このメーリングリストのアーカイブは web 上の多数の場所に存在します。こ
|
||||
れらのアーカイブを探すにはサーチエンジンを使いましょう。例えば-
|
||||
|
||||
http://dir.gmane.org/gmane.linux.kernel
|
||||
https://lore.kernel.org/lkml/
|
||||
|
||||
リストに投稿する前にすでにその話題がアーカイブに存在するかどうかを検索
|
||||
することを是非やってください。多数の事がすでに詳細に渡って議論されてお
|
||||
|
|
|
|||
|
|
@ -386,7 +386,7 @@ https://bugzilla.kernel.org 를 체크하고자 할 수도 있다; 소수의 커
|
|||
웹상의 많은 다른 곳에도 메일링 리스트의 아카이브들이 있다.
|
||||
이러한 아카이브들을 찾으려면 검색 엔진을 사용하라. 예를 들어:
|
||||
|
||||
http://dir.gmane.org/gmane.linux.kernel
|
||||
https://lore.kernel.org/lkml/
|
||||
|
||||
여러분이 새로운 문제에 관해 리스트에 올리기 전에 말하고 싶은 주제에 관한
|
||||
것을 아카이브에서 먼저 찾아보기를 강력히 권장한다. 이미 상세하게 토론된 많은
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
.. SPDX-License-Identifier: GPL-2.0
|
||||
.. include:: ../disclaimer-zh_CN.rst
|
||||
|
||||
:Original: Documentation/Devicetree/changesets.rst
|
||||
:Original: Documentation/devicetree/changesets.rst
|
||||
|
||||
:翻译:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
.. SPDX-License-Identifier: GPL-2.0
|
||||
.. include:: ../disclaimer-zh_CN.rst
|
||||
|
||||
:Original: Documentation/Devicetree/dynamic-resolution-notes.rst
|
||||
:Original: Documentation/devicetree/dynamic-resolution-notes.rst
|
||||
|
||||
:翻译:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
.. SPDX-License-Identifier: GPL-2.0
|
||||
.. include:: ../disclaimer-zh_CN.rst
|
||||
|
||||
:Original: Documentation/Devicetree/kernel-api.rst
|
||||
:Original: Documentation/devicetree/kernel-api.rst
|
||||
|
||||
:翻译:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
.. SPDX-License-Identifier: GPL-2.0
|
||||
.. include:: ../disclaimer-zh_CN.rst
|
||||
|
||||
:Original: Documentation/Devicetree/overlay-notes.rst
|
||||
:Original: Documentation/devicetree/overlay-notes.rst
|
||||
|
||||
:翻译:
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ KSM的用户空间的接口在Documentation/translations/zh_CN/admin-guide/mm/ks
|
|||
KSM维护着稳定树中的KSM页的逆映射信息。
|
||||
|
||||
当KSM页面的共享数小于 ``max_page_sharing`` 的虚拟内存区域(VMAs)时,则代表了
|
||||
KSM页的稳定树其中的节点指向了一个rmap_item结构体类型的列表。同时,这个KSM页
|
||||
KSM页的稳定树其中的节点指向了一个ksm_rmap_item结构体类型的列表。同时,这个KSM页
|
||||
的 ``page->mapping`` 指向了该稳定树节点。
|
||||
|
||||
如果共享数超过了阈值,KSM将给稳定树添加第二个维度。稳定树就变成链接一个或多
|
||||
|
|
|
|||
|
|
@ -74,15 +74,19 @@ page owner在默认情况下是禁用的。所以,如果你想使用它,你
|
|||
cat /sys/kernel/debug/page_owner > page_owner_full.txt
|
||||
./page_owner_sort page_owner_full.txt sorted_page_owner.txt
|
||||
|
||||
``page_owner_full.txt`` 的一般输出情况如下(输出信息无翻译价值)::
|
||||
``page_owner_full.txt`` 的一般输出情况如下::
|
||||
|
||||
Page allocated via order XXX, ...
|
||||
PFN XXX ...
|
||||
// Detailed stack
|
||||
// 栈详情
|
||||
|
||||
Page allocated via order XXX, ...
|
||||
PFN XXX ...
|
||||
// Detailed stack
|
||||
// 栈详情
|
||||
默认情况下,它将以一个给定的pfn开始,做完整的pfn转储,且page_owner支持fseek。
|
||||
|
||||
FILE *fp = fopen("/sys/kernel/debug/page_owner", "r");
|
||||
fseek(fp, pfn_start, SEEK_SET);
|
||||
|
||||
``page_owner_sort`` 工具忽略了 ``PFN`` 行,将剩余的行放在buf中,使用regexp提
|
||||
取页序值,计算buf的次数和页数,最后根据参数进行排序。
|
||||
|
|
|
|||
|
|
@ -306,7 +306,7 @@ bugzilla.kernel.org是Linux内核开发者们用来跟踪内核Bug的网站。
|
|||
网上很多地方都有这个邮件列表的存档(archive)。可以使用搜索引擎来找到这些
|
||||
存档。比如:
|
||||
|
||||
http://dir.gmane.org/gmane.linux.kernel
|
||||
https://lore.kernel.org/lkml/
|
||||
|
||||
在发信之前,我们强烈建议你先在存档中搜索你想要讨论的问题。很多已经被详细
|
||||
讨论过的问题只在邮件列表的存档中可以找到。
|
||||
|
|
|
|||
|
|
@ -309,7 +309,7 @@ bugzilla.kernel.org是Linux內核開發者們用來跟蹤內核Bug的網站。
|
|||
網上很多地方都有這個郵件列表的存檔(archive)。可以使用搜尋引擎來找到這些
|
||||
存檔。比如:
|
||||
|
||||
http://dir.gmane.org/gmane.linux.kernel
|
||||
https://lore.kernel.org/lkml/
|
||||
|
||||
在發信之前,我們強烈建議你先在存檔中搜索你想要討論的問題。很多已經被詳細
|
||||
討論過的問題只在郵件列表的存檔中可以找到。
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user