From: John Hubbard <jhubbard@nvidia.com>
To: Yang Shi <yang.shi@linux.alibaba.com>, <mtk.manpages@gmail.com>,
<cl@linux.com>, <mhocko@suse.com>, <cai@lca.pw>,
<akpm@linux-foundation.org>
Cc: <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: Thu, 5 Dec 2019 17:47:35 -0800 [thread overview]
Message-ID: <683f6cae-0e0c-d4e4-0929-7fd1a79a2266@nvidia.com> (raw)
In-Reply-To: <1575596090-115377-1-git-send-email-yang.shi@linux.alibaba.com>
On 12/5/19 5:34 PM, Yang Shi wrote:
...
>
> 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.
How about this wording (ignoring man formatting for the moment):
No pages were moved, because all requested pages fell into one or more of
the following cases:
* Page not present.
* Page has an invalid address.
* Page is mapped by multiple processes.
Reasoning: I don't like the "no pages were found" all by itself, because it
blindly rewords the meaning of ENOENT. ENOENT is merely the closest
symbol we have. So we use ENOENT and that's fine, but the descriptive text
should describe what really happened, which is "no pages were moved". If we had
an ENOPAGESMOVED then we'd use that. :)
thanks,
--
John Hubbard
NVIDIA
WARNING: multiple messages have this Message-ID (diff)
From: John Hubbard <jhubbard@nvidia.com>
To: Yang Shi <yang.shi@linux.alibaba.com>,
mtk.manpages@gmail.com, cl@linux.com, mhocko@suse.com,
cai@lca.pw, akpm@linux-foundation.org
Cc: 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: Thu, 5 Dec 2019 17:47:35 -0800 [thread overview]
Message-ID: <683f6cae-0e0c-d4e4-0929-7fd1a79a2266@nvidia.com> (raw)
In-Reply-To: <1575596090-115377-1-git-send-email-yang.shi@linux.alibaba.com>
On 12/5/19 5:34 PM, Yang Shi wrote:
...
>
> 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.
How about this wording (ignoring man formatting for the moment):
No pages were moved, because all requested pages fell into one or more of
the following cases:
* Page not present.
* Page has an invalid address.
* Page is mapped by multiple processes.
Reasoning: I don't like the "no pages were found" all by itself, because it
blindly rewords the meaning of ENOENT. ENOENT is merely the closest
symbol we have. So we use ENOENT and that's fine, but the descriptive text
should describe what really happened, which is "no pages were moved". If we had
an ENOPAGESMOVED then we'd use that. :)
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2019-12-06 1:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 1:34 [PATCH] move_pages.2: not return ENOENT if the page are already on the target nodes Yang Shi
2019-12-06 1:47 ` John Hubbard [this message]
2019-12-06 1:47 ` John Hubbard
2019-12-06 7:47 ` Michal Hocko
2019-12-06 8:25 ` John Hubbard
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 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 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
2019-12-31 3:49 ` Eric W. Biederman
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=683f6cae-0e0c-d4e4-0929-7fd1a79a2266@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=cl@linux.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=mhocko@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.