From: Oleksandr Natalenko <oleksandr@redhat.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
linux-mm <linux-mm@kvack.org>,
linux-api@vger.kernel.org, Suren Baghdasaryan <surenb@google.com>,
Tim Murray <timmurray@google.com>,
Sandeep Patil <sspatil@google.com>,
Sonny Rao <sonnyrao@google.com>,
Brian Geffon <bgeffon@google.com>, Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Shakeel Butt <shakeelb@google.com>,
John Dias <joaodias@google.com>,
Joel Fernandes <joel@joelfernandes.org>,
Jann Horn <jannh@google.com>,
alexander.h.duyck@linux.intel.com, sj38.park@gmail.com,
David Rientjes <rientjes@google.com>,
Arjun Roy <arjunroy@google.com>
Subject: Re: [PATCH v8 0/4] introduce memory hinting API for external process
Date: Tue, 23 Jun 2020 11:07:21 +0200 [thread overview]
Message-ID: <20200623090721.5owt4cxjji6isqe3@butterfly.localdomain> (raw)
In-Reply-To: <20200622192900.22757-1-minchan@kernel.org>
On Mon, Jun 22, 2020 at 12:28:56PM -0700, Minchan Kim wrote:
> Now, we have MADV_PAGEOUT and MADV_COLD as madvise hinting API. With that,
> application could give hints to kernel what memory range are preferred to be
> reclaimed. However, in some platform(e.g., Android), the information
> required to make the hinting decision is not known to the app.
> Instead, it is known to a centralized userspace daemon(e.g., ActivityManagerService),
> and that daemon must be able to initiate reclaim on its own without any app
> involvement.
>
> To solve the concern, this patch introduces new syscall - process_madvise(2).
> Bascially, it's same with madvise(2) syscall but it has some differences.
>
> 1. It needs pidfd of target process to provide the hint
> 2. It supports only MADV_{COLD|PAGEOUT} at this moment.
> Other hints in madvise will be opened when there are explicit requests from
> community to prevent unexpected bugs we couldn't support.
> 3. Only privileged processes can do something for other process's address
> space.
>
> For more detail of the new API, please see "mm: introduce external memory hinting API"
> description in this patchset.
>
> * from v7 - http://lore.kernel.org/r/20200302193630.68771-1-minchan@kernel.org
> * dropping pid support from new syscall and fold releated patches into syscall patch
> * dropping KSM patch by discussion - Oleksandr, I lost the discussion.
> Please resend the single patch against of the patchset if you resolves the discussion.
> https://lore.kernel.org/linux-api/20200302193630.68771-8-minchan@kernel.org/
What "next" tag this (v8) submission is based on please?
> * from v6 - https://lore.kernel.org/linux-api/20200219014433.88424-1-minchan@kernel.org/
> * fix comments and descriptions - Suren
> * Add Reviewed-by - Suren
> * fix build break reported by 0-day
>
> * from v5 - https://lore.kernel.org/linux-mm/20200214170520.160271-1-minchan@kernel.org/
> * use null task and requestor's mm for io_madvise - Jann and Jens
> * use right commit description for moving pidfd_get_pid - Christoph
>
> * from v4 - https://lore.kernel.org/linux-mm/20200212233946.246210-1-minchan@kernel.org/
> * pass mm down to functions, not accessing task->mm - Jann
> * clean up - Alexander
> * add Reviewed-by - Alexander, SeongJae
> * patch reordering
>
> * from v3 - https://lore.kernel.org/linux-mm/20200128001641.5086-1-minchan@kernel.org/
> * verify task->mm aftere access_mm - Oleg
> * split some patches for easy review - Alexander
> * clean up fatal signal checking - Suren
>
> * from v2 - https://lore.kernel.org/linux-mm/20200116235953.163318-1-minchan@kernel.org/
> * check signal callee and caller to bail out - Kirill Tkhai
> * put more clarification for justification of new API
>
> * from v1 - https://lore.kernel.org/linux-mm/20200110213433.94739-1-minchan@kernel.org/
> * fix syscall number - SeongJae
> * use get_pid_task - Kirill Tkhai
> * extend API to support pid as well as pidfd - Kirill Tkhai
>
> Minchan Kim (4):
> mm/madvise: pass task and mm to do_madvise
> pid: move pidfd_get_pid() to pid.c
> mm/madvise: introduce process_madvise() syscall: an external memory
> hinting API
> mm/madvise: check fatal signal pending of target process
>
> arch/alpha/kernel/syscalls/syscall.tbl | 1 +
> arch/arm/tools/syscall.tbl | 1 +
> arch/arm64/include/asm/unistd.h | 2 +-
> arch/arm64/include/asm/unistd32.h | 2 +
> arch/ia64/kernel/syscalls/syscall.tbl | 1 +
> arch/m68k/kernel/syscalls/syscall.tbl | 1 +
> arch/microblaze/kernel/syscalls/syscall.tbl | 1 +
> arch/mips/kernel/syscalls/syscall_n32.tbl | 1 +
> arch/mips/kernel/syscalls/syscall_n64.tbl | 1 +
> arch/mips/kernel/syscalls/syscall_o32.tbl | 1 +
> arch/parisc/kernel/syscalls/syscall.tbl | 1 +
> arch/powerpc/kernel/syscalls/syscall.tbl | 1 +
> arch/s390/kernel/syscalls/syscall.tbl | 1 +
> arch/sh/kernel/syscalls/syscall.tbl | 1 +
> arch/sparc/kernel/syscalls/syscall.tbl | 1 +
> arch/x86/entry/syscalls/syscall_32.tbl | 1 +
> arch/x86/entry/syscalls/syscall_64.tbl | 2 +
> arch/xtensa/kernel/syscalls/syscall.tbl | 1 +
> fs/io_uring.c | 2 +-
> include/linux/compat.h | 4 +
> include/linux/mm.h | 3 +-
> include/linux/pid.h | 1 +
> include/linux/syscalls.h | 2 +
> include/uapi/asm-generic/unistd.h | 4 +-
> kernel/exit.c | 17 --
> kernel/pid.c | 17 ++
> kernel/sys_ni.c | 2 +
> mm/madvise.c | 190 +++++++++++++++++---
> 28 files changed, 217 insertions(+), 46 deletions(-)
>
> --
> 2.27.0.111.gc72c7da667-goog
>
--
Best regards,
Oleksandr Natalenko (post-factum)
Principal Software Maintenance Engineer
next prev parent reply other threads:[~2020-06-23 9:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 19:28 [PATCH v8 0/4] introduce memory hinting API for external process Minchan Kim
2020-06-22 19:28 ` [PATCH v8 1/4] mm/madvise: pass task and mm to do_madvise Minchan Kim
2020-06-24 20:00 ` David Rientjes
2020-06-22 19:28 ` [PATCH v8 2/4] pid: move pidfd_get_pid() to pid.c Minchan Kim
2020-06-24 20:00 ` David Rientjes
2020-06-22 19:28 ` [PATCH v8 3/4] mm/madvise: introduce process_madvise() syscall: an external memory hinting API Minchan Kim
2020-06-24 20:00 ` David Rientjes
2020-06-25 20:38 ` Minchan Kim
2020-08-28 17:40 ` Arnd Bergmann
2020-08-28 18:24 ` Jens Axboe
2020-08-28 18:25 ` Christian Brauner
2020-08-28 19:04 ` Minchan Kim
2020-08-28 19:26 ` Jens Axboe
2020-08-28 20:15 ` Arnd Bergmann
2020-08-29 7:02 ` Christoph Hellwig
2020-06-22 19:29 ` [PATCH v8 4/4] mm/madvise: check fatal signal pending of target process Minchan Kim
2020-06-24 20:00 ` David Rientjes
2020-06-22 19:36 ` [PATCH v8 0/4] introduce memory hinting API for external process Minchan Kim
2020-06-23 8:59 ` Oleksandr Natalenko
2020-06-23 9:07 ` Oleksandr Natalenko [this message]
2020-06-24 1:31 ` Minchan Kim
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=20200623090721.5owt4cxjji6isqe3@butterfly.localdomain \
--to=oleksandr@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=arjunroy@google.com \
--cc=bgeffon@google.com \
--cc=christian.brauner@ubuntu.com \
--cc=hannes@cmpxchg.org \
--cc=jannh@google.com \
--cc=joaodias@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=sj38.park@gmail.com \
--cc=sonnyrao@google.com \
--cc=sspatil@google.com \
--cc=surenb@google.com \
--cc=timmurray@google.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;
as well as URLs for NNTP newsgroup(s).