.TP
\fBMADV_HWPOISON\fP (Linux 2.6.32 以降)
Poison a page and handle it like a hardware memory corruption. This
-operation is only available for privileged (\fBCAP_SYS_ADMIN\fP) processes.
+operation is available only for privileged (\fBCAP_SYS_ADMIN\fP) processes.
This operation may result in the calling process receiving a \fBSIGBUS\fP and
the page being unmapped. This feature is intended for testing of memory
-error\-handling code; it is only available if the kernel was configured with
+error\-handling code; it is available only if the kernel was configured with
\fBCONFIG_MEMORY_FAILURE\fP.
.TP
\fBMADV_SOFT_OFFLINE\fP (Linux 2.6.33 以降)
out of normal memory management). The effect of the \fBMADV_SOFT_OFFLINE\fP
operation is invisible to (i.e., does not change the semantics of) the
calling process. This feature is intended for testing of memory
-error\-handling code; it is only available if the kernel was configured with
+error\-handling code; it is available only if the kernel was configured with
\fBCONFIG_MEMORY_FAILURE\fP.
.TP
\fBMADV_MERGEABLE\fP (Linux 2.6.32 以降)
memory that have been marked as mergeable, looking for pages with identical
content. These are replaced by a single write\-protected page (which is
automatically copied if a process later wants to update the content of the
-page). KSM only merges private anonymous pages (see \fBmmap\fP(2)). The KSM
+page). KSM merges only private anonymous pages (see \fBmmap\fP(2)). The KSM
feature is intended for applications that generate many instances of the
same data (e.g., virtualization systems such as KVM). It can consume a lot
of processing power; use with care. See the Linux kernel source file
\fIDocumentation/vm/ksm.txt\fP for more details. The \fBMADV_MERGEABLE\fP and
-\fBMADV_UNMERGEABLE\fP operations are only available if the kernel was
+\fBMADV_UNMERGEABLE\fP operations are available only if the kernel was
configured with \fBCONFIG_KSM\fP.
.TP
\fBMADV_UNMERGEABLE\fP (Linux 2.6.32 以降)
.\" http://lwn.net/Articles/358904/
.\" https://lwn.net/Articles/423584/
Enables Transparent Huge Pages (THP) for pages in the range specified by
-\fIaddr\fP and \fIlength\fP. Currently, Transparent Huge Pages only work with
+\fIaddr\fP and \fIlength\fP. Currently, Transparent Huge Pages work only with
private anonymous pages (see \fBmmap\fP(2)). The kernel will regularly scan
the areas marked as huge page candidates to replace them with huge pages.
The kernel will also allocate huge pages directly when the region is
that only ever accesses 1 byte will result in 2MB of wired memory instead of
one 4KB page). See the Linux kernel source file
\fIDocumentation/vm/transhuge.txt\fP for more details. The \fBMADV_HUGEPAGE\fP
-and \fBMADV_NOHUGEPAGE\fP operations are only available if the kernel was
+and \fBMADV_NOHUGEPAGE\fP operations are available only if the kernel was
configured with \fBCONFIG_TRANSPARENT_HUGEPAGE\fP.
.TP
\fBMADV_NOHUGEPAGE\fP (Linux 2.6.38 以降)
指定したマップは存在するが、ファイルではないところをマップしている。
.TP
\fBEINVAL\fP
-This error can occur for the following reasons:
+このエラーは以下の理由で発生する。
.RS
.IP * 3
.\" .I len
.\" is zero,
\fIlen\fP が負の値である。
.IP *
-\fIaddr\fP is not page\-aligned.
+\fIaddr\fP がページ境界ではない。
.IP *
\fIadvice\fP が有効な値でない。
.IP *
アプリケーションがロックされたページや共有ページを (\fBMADV_DONTNEED\fP で) 解放
しようとしている。
.IP *
-\fBMADV_MERGEABLE\fP or \fBMADV_UNMERGEABLE\fP was specified in \fIadvice\fP, but the
-kernel was not configured with \fBCONFIG_KSM\fP.
+\fIadvice\fP に \fBMADV_MERGEABLE\fP か \fBMADV_UNMERGEABLE\fP が指定されたが、 カーネルの設定が
+\fBCONFIG_KSM\fP が有効になっていなかった。
.RE
.TP
\fBEIO\fP
\fBMADV_REMOVE\fP, \fBMADV_DONTFORK\fP, \fBMADV_DOFORK\fP, \fBMADV_HWPOISON\fP,
\fBMADV_MERGEABLE\fP, \fBMADV_UNMERGEABLE\fP は Linux 固有である。
.SH 注意
-.SS "Linux notes"
+.SS "Linux での注意"
.LP
現在の Linux の実装 (2.4.0) では、 このシステムコールをアドバイスというよりは命令と見ている。
したがってこのアドバイスに対して通常行われる動作が不可能な場合は、 エラーを返すことがある (上記の エラー の記述を参照)。
\fBgetrlimit\fP(2), \fBmincore\fP(2), \fBmmap\fP(2), \fBmprotect\fP(2), \fBmsync\fP(2),
\fBmunmap\fP(2), \fBcore\fP(5)
.SH この文書について
-この man ページは Linux \fIman\-pages\fP プロジェクトのリリース 3.50 の一部
+この man ページは Linux \fIman\-pages\fP プロジェクトのリリース 3.52 の一部
である。プロジェクトの説明とバグ報告に関する情報は
http://www.kernel.org/doc/man\-pages/ に書かれている。