From: Michal Hocko <mhocko@kernel.org>
To: Yang Shi <yang.shi@linux.alibaba.com>
Cc: mtk.manpages@gmail.com, cl@linux.com, jhubbard@nvidia.com,
cai@lca.pw, akpm@linux-foundation.org, linux-man@vger.kernel.org,
linux-api@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] move_pages.2: not return ENOENT if the page are already on the target nodes
Date: Fri, 6 Dec 2019 08:47:56 +0100 [thread overview]
Message-ID: <20191206074756.GI28317@dhcp22.suse.cz> (raw)
In-Reply-To: <1575596090-115377-1-git-send-email-yang.shi@linux.alibaba.com>
On Fri 06-12-19 09:34:50, Yang Shi wrote:
> Since commit e78bbfa82624 ("mm: stop returning -ENOENT
> from sys_move_pages() if nothing got migrated"), move_pages doesn't
> return -ENOENT anymore if the pages are already on the target nodes, but
> this change is never reflected in manpage.
>
> Cc: Michael Kerrisk <mtk.manpages@gmail.com>
> Cc: Christoph Lameter <cl@linux.com>
> Cc: John Hubbard <jhubbard@nvidia.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Qian Cai <cai@lca.pw>
> Signed-off-by: Yang Shi <yang.shi@linux.alibaba.com>
> ---
> man2/move_pages.2 | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/man2/move_pages.2 b/man2/move_pages.2
> index 2d96468..2a2f3cd 100644
> --- a/man2/move_pages.2
> +++ b/man2/move_pages.2
> @@ -192,9 +192,8 @@ was specified or an attempt was made to migrate pages of a kernel thread.
> One of the target nodes is not online.
> .TP
> .B ENOENT
> -No pages were found that require moving.
> -All pages are either already
> -on the target node, not present, had an invalid address or could not be
> +No pages were found.
> +All pages are either not present, had an invalid address or could not be
> moved because they were mapped by multiple processes.
I would rather not put any specifics here because those reasons might
differ in future. I would simply go with "No pages were found that
require or could be moved."
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-12-06 7:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 1:34 Yang Shi
2019-12-06 1:47 ` John Hubbard
2019-12-06 7:47 ` Michal Hocko [this message]
2019-12-06 8:25 ` John Hubbard
2019-12-06 9:45 ` Michal Hocko
2019-12-06 17:31 ` Yang Shi
2019-12-06 18:00 ` Qian Cai
2019-12-06 18:19 ` Christopher Lameter
2019-12-06 17:26 ` Yang Shi
2019-12-14 1:55 ` Michael Kerrisk (man-pages)
2019-12-18 7:36 ` John Hubbard
2019-12-18 10:17 ` Michal Hocko
2019-12-31 3:00 ` Yang Shi
2019-12-31 3:49 ` Eric W. Biederman
2020-01-02 22:15 ` Yang Shi
2019-12-31 2:49 ` Yang Shi
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=20191206074756.GI28317@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=cl@linux.com \
--cc=jhubbard@nvidia.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=yang.shi@linux.alibaba.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