[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 07 Jul 2021 11:46:42 +0200
From: Florian Weimer <fweimer@...hat.com>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: akpm@...ux-foundation.org, mhocko@...nel.org, mhocko@...e.com,
rientjes@...gle.com, willy@...radead.org, hannes@...xchg.org,
guro@...com, riel@...riel.com, minchan@...nel.org,
christian@...uner.io, hch@...radead.org, oleg@...hat.com,
david@...hat.com, jannh@...gle.com, shakeelb@...gle.com,
timmurray@...gle.com, linux-api@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
kernel-team@...roid.com
Subject: Re: [PATCH 1/1] mm: introduce process_reap system call
* Suren Baghdasaryan:
> The API is as follows,
>
> int process_reap(int pidfd, unsigned int flags);
>
> DESCRIPTION
> The process_reap() system call is used to free the memory of a
> dying process.
>
> The pidfd selects the process referred to by the PID file
> descriptor.
> (See pidofd_open(2) for further information)
>
> The flags argument is reserved for future use; currently, this
> argument must be specified as 0.
>
> RETURN VALUE
> On success, process_reap() returns 0. On error, -1 is returned
> and errno is set to indicate the error.
I think the manual page should mention what it means for a process to be
“dying”, and how to move a process to this state.
Thanks,
Florian
Powered by blists - more mailing lists