From: Oscar Salvador <osalvador@suse.de>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: Jiaqi Yan <jiaqiyan@google.com>,
nao.horiguchi@gmail.com, jane.chu@oracle.com,
muchun.song@linux.dev, akpm@linux-foundation.org,
shuah@kernel.org, corbet@lwn.net, rientjes@google.com,
duenwen@google.com, fvdl@google.com, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
Lance Yang <ioworker0@gmail.com>
Subject: Re: [PATCH v2 1/3] mm/memory-failure: userspace controls soft-offlining pages
Date: Mon, 17 Jun 2024 09:51:01 +0200 [thread overview]
Message-ID: <ea8c5e390bd18c532b768dd9eeaa105a@suse.de> (raw)
In-Reply-To: <786a08ff-aa7e-49d5-f589-0a405c7e1a34@huawei.com>
On 2024-06-17 09:31, Miaohe Lin wrote:
> IMHO, it might not be suitable to use EAGAIN. Because it means
> "Resource temporarily unavailable" and
> this can be solved by simply retry later without any further actions
> taken. But I might be wrong.
We usually use 'EOPNOTSUPP' when we fail due to a setting not being set.
EPERM is more for a capability matter.
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2024-06-17 7:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 21:55 [PATCH v2 0/3] Userspace controls soft-offline pages Jiaqi Yan
2024-06-11 21:55 ` [PATCH v2 1/3] mm/memory-failure: userspace controls soft-offlining pages Jiaqi Yan
2024-06-14 3:28 ` Miaohe Lin
2024-06-14 16:40 ` Jiaqi Yan
2024-06-14 8:35 ` Lance Yang
2024-06-14 16:30 ` Jiaqi Yan
2024-06-17 7:31 ` Miaohe Lin
2024-06-17 7:51 ` Oscar Salvador [this message]
2024-06-17 8:16 ` Miaohe Lin
2024-06-17 10:34 ` Lance Yang
2024-06-17 15:42 ` Jiaqi Yan
2024-06-11 21:55 ` [PATCH v2 2/3] selftest/mm: test enable_soft_offline behaviors Jiaqi Yan
2024-06-14 3:50 ` Miaohe Lin
2024-06-14 19:36 ` Jiaqi Yan
2024-06-11 21:55 ` [PATCH v2 3/3] docs: mm: add enable_soft_offline sysctl Jiaqi Yan
2024-06-12 0:25 ` David Rientjes
2024-06-14 23:15 ` Jiaqi Yan
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=ea8c5e390bd18c532b768dd9eeaa105a@suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=duenwen@google.com \
--cc=fvdl@google.com \
--cc=ioworker0@gmail.com \
--cc=jane.chu@oracle.com \
--cc=jiaqiyan@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=rientjes@google.com \
--cc=shuah@kernel.org \
/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