From: Michal Hocko <mhocko@suse.com>
To: Frank van der Linden <fvdl@google.com>
Cc: Zhongkun He <hezhongkun.hzk@bytedance.com>,
corbet@lwn.net, akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-doc@vger.kernel.org, wuyun.abel@bytedance.com
Subject: Re: [RFC] mm: add new syscall pidfd_set_mempolicy()
Date: Tue, 11 Oct 2022 17:00:14 +0200 [thread overview]
Message-ID: <Y0WE/lEiNvl2ljo1@dhcp22.suse.cz> (raw)
In-Reply-To: <CAPTztWYTGOb8ZQzfgThqJn+fyi4ZB8=JQQZi5_rUoDhdftKtvg@mail.gmail.com>
On Mon 10-10-22 09:22:13, Frank van der Linden wrote:
> For consistency with process_madvise(), I would suggest calling it
> process_set_mempolicy.
This operation has per-thread rather than per-process semantic so I do
not think your proposed naming is better.
> Other than that, this makes sense. To complete
> the set, perhaps a process_mbind() should be added as well. What do
> you think?
Is there any real usecase for this interface? How is the caller supposed
to make per-range decisions without a very involved coordination with
the target process?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2022-10-11 15:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 9:48 [RFC] mm: add new syscall pidfd_set_mempolicy() Zhongkun He
2022-10-10 16:22 ` Frank van der Linden
2022-10-11 15:00 ` Michal Hocko [this message]
2022-10-11 17:22 ` Frank van der Linden
2022-10-11 19:29 ` Michal Hocko
2022-10-12 3:14 ` Abel Wu
2022-10-12 12:34 ` Vinicius Petrucci
2022-10-12 13:07 ` Michal Hocko
2022-10-12 13:23 ` Michal Hocko
2022-10-12 16:51 ` Frank van der Linden
2022-10-11 14:57 ` Michal Hocko
2022-10-12 7:55 ` [External] " Zhongkun He
2022-10-12 9:02 ` Michal Hocko
2022-10-12 11:22 ` Zhongkun He
2022-10-12 12:15 ` Michal Hocko
2022-10-13 10:44 ` Zhongkun He
2022-10-13 11:26 ` Michal Hocko
2022-10-13 12:50 ` Zhongkun He
2022-10-13 13:17 ` Michal Hocko
2022-10-13 13:42 ` Zhongkun He
2022-10-12 4:16 ` Bagas Sanjaya
2022-10-12 8:18 ` [External] " Zhongkun He
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=Y0WE/lEiNvl2ljo1@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=fvdl@google.com \
--cc=hezhongkun.hzk@bytedance.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wuyun.abel@bytedance.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