From: Christoph Lameter <cl@linux.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Piotr Kwapulinski <kwapulinski.piotr@gmail.com>,
mhocko@kernel.org, mgorman@techsingularity.net,
a.p.zijlstra@chello.nl, riel@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-man@vger.kernel.org,
Brice Goglin <Brice.Goglin@inria.fr>
Subject: Re: Rewording language in mbind(2) to "threads" not "processes"
Date: Thu, 13 Oct 2016 13:16:21 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1610131314020.3176@east.gentwo.org> (raw)
In-Reply-To: <f3c4ca9d-a880-5244-e06e-db4725e4d945@gmail.com>
On Thu, 13 Oct 2016, Michael Kerrisk (man-pages) wrote:
> @@ -100,7 +100,10 @@ If, however, the shared memory region was created with the
> .B SHM_HUGETLB
> flag,
> the huge pages will be allocated according to the policy specified
> -only if the page allocation is caused by the process that calls
> +only if the page allocation is caused by the thread that calls
> +.\"
> +.\" ??? Is it correct to change "process" to "thread" in the preceding line?
No leave it as process. Pages get one map refcount per page table
that references them (meaning a process). More than one map refcount means
that multiple processes have mapped the page.
> @@ -300,7 +303,10 @@ is specified in
> .IR flags ,
> then the kernel will attempt to move all the existing pages
> in the memory range so that they follow the policy.
> -Pages that are shared with other processes will not be moved.
> +Pages that are shared with other threads will not be moved.
> +.\"
> +.\" ??? Is it correct to change "processes" to "threads" in the preceding line?
> +.\"
Leave it. Same as before.
> If
> then the kernel will attempt to move all existing pages in the memory range
> -regardless of whether other processes use the pages.
> -The calling process must be privileged
> +regardless of whether other threads use the pages.
> +.\"
> +.\" ??? Is it correct to change "processes" to "threads" in the preceding line?
> +.\"
Leave as process.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-10-13 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 8:38 Michael Kerrisk (man-pages)
2016-10-13 18:16 ` Christoph Lameter [this message]
2016-10-14 10:09 ` Michael Kerrisk (man-pages)
2016-10-21 7:22 ` Michael Kerrisk (man-pages)
2016-10-21 13:44 ` Christoph Lameter
2016-10-22 10:08 ` Michael Kerrisk (man-pages)
2016-10-22 10:08 ` Michael Kerrisk (man-pages)
2016-10-25 15:40 ` Piotr Kwapulinski
2016-10-31 11:59 ` Michael Kerrisk (man-pages)
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=alpine.DEB.2.20.1610131314020.3176@east.gentwo.org \
--to=cl@linux.com \
--cc=Brice.Goglin@inria.fr \
--cc=a.p.zijlstra@chello.nl \
--cc=kwapulinski.piotr@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=riel@redhat.com \
/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