From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-18.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 42105C4338F for ; Mon, 9 Aug 2021 18:56:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 24E0660FE3 for ; Mon, 9 Aug 2021 18:56:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235853AbhHIS5A (ORCPT ); Mon, 9 Aug 2021 14:57:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50412 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235765AbhHIS5A (ORCPT ); Mon, 9 Aug 2021 14:57:00 -0400 Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C32B3C061796 for ; Mon, 9 Aug 2021 11:56:39 -0700 (PDT) Received: by mail-pj1-x102a.google.com with SMTP id fa24-20020a17090af0d8b0290178bfa69d97so1514240pjb.0 for ; Mon, 09 Aug 2021 11:56:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rZnS5Yg8Ungl0NoSfe0iR6+HFsdNXlz+2LHGqQJxvwo=; b=bwoE5zejhZCxyq+WyMKCe4nXWa5tO89iRvDhnlFHiCRzHi8k4EyOEpcvSOKWw8ui9t IOHeyYKndJnQwJhk7IkL6+dil9dvBZ9jKtZyMkUuKUjgVpkbJOFjWytz+vBp5EeOp0FA vzHcolzrdP/9CjzGPAY0oGu72yGbpfm5Gn6h55tOlldPTsuV6BMlA/irMvUnQ+aqQoZW 0p72/A/xm7ZYKBiyli/ctS30ECBO4FD/LfeDjwoC7UiBeiQa750HX3UeQkFPAN0FN5ZF 9rys4gNBkRwSxpR/fOIawV5651K6f7jV/G+lZfpaVJxlSTDfyFbSV0i5Yq1DqG5PgxOe JL0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rZnS5Yg8Ungl0NoSfe0iR6+HFsdNXlz+2LHGqQJxvwo=; b=FM19oM2YthkM8sa89MhJRM8fxkKNKmDluG3EpH6qX4n2LL6obzfqbMDZDxwLk1vAs1 LNIo701UYyfz6QCs2XGdI2kLCqob4K01WtbDp0TIOVtzrVSqvHZfz3R7e2ynmHPapB5q At+U6igLzIEkjAm+9QVEs7Z2vZUJsWGwotQam2ioGcgI8GQG0wH3B8Fh91tXb8AGTxZz 9NedoTz1CUCcmVWRssJZV0ZAKG3ZAr7xQLOUdL33oKPpTLQ4Xp6PHYpNjICOca4SdtBV B0tQ0VddvyVHYduBgfuC2ewvcYF6+UD+28OlFeyGrtaLPOq/gMPgt1OjGQPMNlTc1e7m t0RQ== X-Gm-Message-State: AOAM532lrfYtX7JsKXJhXK9d0dYGjAzXyVo/ssS0JB7MPgWfcxz2gzey KpTShnW/w+bfxswlj0Q7JOpf6s8Vwgje/8ze0rCkPg== X-Google-Smtp-Source: ABdhPJxjaqkLW6MmJ+c8T9DwC9JWTtlsFJVi3w9OFPIZvA0UgCpNZOngvNOAK/gUwWSpb8bAkZyYtzuh0uESzMCUs3g= X-Received: by 2002:a63:f342:: with SMTP id t2mr465315pgj.45.1628535398993; Mon, 09 Aug 2021 11:56:38 -0700 (PDT) MIME-Version: 1.0 References: <20210808160823.3553954-1-surenb@google.com> In-Reply-To: From: Suren Baghdasaryan Date: Mon, 9 Aug 2021 11:56:28 -0700 Message-ID: Subject: Re: [PATCH v8 1/2] mm: introduce process_mrelease system call To: Shakeel Butt Cc: Andrew Morton , Michal Hocko , Michal Hocko , David Rientjes , Matthew Wilcox , Johannes Weiner , Roman Gushchin , Rik van Riel , Minchan Kim , Christian Brauner , Christoph Hellwig , Oleg Nesterov , David Hildenbrand , Jann Horn , Andy Lutomirski , Christian Brauner , Florian Weimer , Jan Engelhardt , Tim Murray , Linux API , Linux MM , LKML , kernel-team Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-api@vger.kernel.org On Mon, Aug 9, 2021 at 9:23 AM Suren Baghdasaryan wrote: > > On Mon, Aug 9, 2021 at 8:23 AM Shakeel Butt wrote: > > > > On Sun, Aug 8, 2021 at 9:08 AM Suren Baghdasaryan wrote: > > > > > > In modern systems it's not unusual to have a system component monitoring > > > memory conditions of the system and tasked with keeping system memory > > > pressure under control. One way to accomplish that is to kill > > > non-essential processes to free up memory for more important ones. > > > Examples of this are Facebook's OOM killer daemon called oomd and > > > Android's low memory killer daemon called lmkd. > > > For such system component it's important to be able to free memory > > > quickly and efficiently. Unfortunately the time process takes to free > > > up its memory after receiving a SIGKILL might vary based on the state > > > of the process (uninterruptible sleep), size and OPP level of the core > > > the process is running. A mechanism to free resources of the target > > > process in a more predictable way would improve system's ability to > > > control its memory pressure. > > > Introduce process_mrelease system call that releases memory of a dying > > > process from the context of the caller. This way the memory is freed in > > > a more controllable way with CPU affinity and priority of the caller. > > > The workload of freeing the memory will also be charged to the caller. > > > The operation is allowed only on a dying process. > > > > > > After previous discussions [1, 2, 3] the decision was made [4] to introduce > > > a dedicated system call to cover this use case. > > > > > > The API is as follows, > > > > > > int process_mrelease(int pidfd, unsigned int flags); > > > > > > DESCRIPTION > > > The process_mrelease() system call is used to free the memory of > > > an exiting process. > > > > > > The pidfd selects the process referred to by the PID file > > > descriptor. > > > (See pidfd_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_mrelease() returns 0. On error, -1 is > > > returned and errno is set to indicate the error. > > > > > > ERRORS > > > EBADF pidfd is not a valid PID file descriptor. > > > > > > EAGAIN Failed to release part of the address space. > > > > > > EINTR The call was interrupted by a signal; see signal(7). > > > > > > EINVAL flags is not 0. > > > > > > EINVAL The memory of the task cannot be released because the > > > process is not exiting, the address space is shared > > > with another live process or there is a core dump in > > > progress. > > > > > > ENOSYS This system call is not supported, for example, without > > > MMU support built into Linux. > > > > > > ESRCH The target process does not exist (i.e., it has terminated > > > and been waited on). > > > > > > [1] https://lore.kernel.org/lkml/20190411014353.113252-3-surenb@google.com/ > > > [2] https://lore.kernel.org/linux-api/20201113173448.1863419-1-surenb@google.com/ > > > [3] https://lore.kernel.org/linux-api/20201124053943.1684874-3-surenb@google.com/ > > > [4] https://lore.kernel.org/linux-api/20201223075712.GA4719@lst.de/ > > > > > > Signed-off-by: Suren Baghdasaryan > > > > Reviewed-by: Shakeel Butt > > Thanks folks! I'll make the change Christian suggested and will push > the next version carrying Acks along, including the one from David > which I forgot to carry in this one. v9 posted at: https://lore.kernel.org/linux-mm/20210809185259.405936-1-surenb@google.com