From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Zhongkun He <hezhongkun.hzk-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
Cc: lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org,
hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Phishing Risk] Re: [Phishing Risk] [External] Re: [PATCH] cgroup/cpuset: Add a new isolated mems.policy type.
Date: Wed, 7 Sep 2022 05:26:09 -1000 [thread overview]
Message-ID: <Yxi4EYxMaPNkL+of@slm.duckdns.org> (raw)
In-Reply-To: <d323bd95-476b-0901-855e-14c8796d1b23-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
Hello,
On Wed, Sep 07, 2022 at 08:06:30PM +0800, Zhongkun He wrote:
> It would be better if one process had a way to dynamically modify the
> mempolicy of another process. But unfortunately there is no interface or
> system call to do that in userspace.
If you need to change the properties dynamically, I suggest adding this as a
dynamic per-process interface first. That's more generic and useful for more
cases.
Thanks.
--
tejun
next prev parent reply other threads:[~2022-09-07 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 6:33 [PATCH] cgroup/cpuset: Add a new isolated mems.policy type hezhongkun
2022-09-02 9:14 ` kernel test robot
[not found] ` <20220902063303.1057-1-hezhongkun.hzk-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
2022-09-02 10:00 ` kernel test robot
2022-09-04 19:42 ` Tejun Heo
[not found] ` <YxT/liaotbiOod51-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2022-09-05 10:30 ` [Phishing Risk] [External] " Zhongkun He
[not found] ` <c05bdeac-b354-0ac7-3233-27f8e5cbb38a-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
2022-09-06 17:19 ` Tejun Heo
[not found] ` <YxeBGeOaQxvlPLzo-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2022-09-07 12:06 ` [Phishing Risk] " Zhongkun He
[not found] ` <d323bd95-476b-0901-855e-14c8796d1b23-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
2022-09-07 15:26 ` Tejun Heo [this message]
2022-09-09 3:00 ` [Phishing Risk] " 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=Yxi4EYxMaPNkL+of@slm.duckdns.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=hezhongkun.hzk-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.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