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=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 48349C388F9 for ; Wed, 4 Nov 2020 06:58:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E6C5B2225B for ; Wed, 4 Nov 2020 06:58:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=suse.com header.i=@suse.com header.b="fWPFaMDj" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727753AbgKDG6s (ORCPT ); Wed, 4 Nov 2020 01:58:48 -0500 Received: from mx2.suse.de ([195.135.220.15]:42912 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725926AbgKDG6s (ORCPT ); Wed, 4 Nov 2020 01:58:48 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1604473126; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ra0pA3cWeHuZF5CggPjlzz66mKrMQ6UHpHMF45ZqqGU=; b=fWPFaMDjoG2mAGPJzk2IauHuUwtE6UB3Ybx/QIP8FxN7cDFNu4xRNi8U+M/F7HNFmWTDLt 80xjtoUzW8zNZRLqOS5lv2G8b2lEfJ+2z2p0uTBydm56Ef98soXF024ScQNlnKqMPiZ9S0 Bdoq+TJzW7WZTspLNHF0lbKtUPLcP+k= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 31569ADE1; Wed, 4 Nov 2020 06:58:46 +0000 (UTC) Date: Wed, 4 Nov 2020 07:58:44 +0100 From: Michal Hocko To: Minchan Kim Cc: Suren Baghdasaryan , linux-api@vger.kernel.org, linux-mm , Andrew Morton , David Rientjes , Matthew Wilcox , Johannes Weiner , Roman Gushchin , Rik van Riel , Christian Brauner , Oleg Nesterov , Tim Murray , kernel-team , LKML , Mel Gorman Subject: Re: [RFC]: userspace memory reaping Message-ID: <20201104065844.GM21990@dhcp22.suse.cz> References: <20201014120937.GC4440@dhcp22.suse.cz> <20201015092030.GB22589@dhcp22.suse.cz> <20201103093550.GE21990@dhcp22.suse.cz> <20201103213228.GB1631979@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201103213228.GB1631979@google.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 03-11-20 13:32:28, Minchan Kim wrote: > On Tue, Nov 03, 2020 at 10:35:50AM +0100, Michal Hocko wrote: > > On Mon 02-11-20 12:29:24, Suren Baghdasaryan wrote: > > [...] > > > To follow up on this. Should I post an RFC implementing SIGKILL_SYNC > > > which in addition to sending a kill signal would also reap the > > > victim's mm in the context of the caller? Maybe having some code will > > > get the discussion moving forward? > > > > Yeah, having a code, even preliminary, might help here. This definitely > > needs a good to go from process management people as that proper is land > > full of surprises... > > Just to remind a idea I suggested to reuse existing concept > > fd = pidfd_open(victim process) > fdatasync(fd); > close(fd); I must have missed this proposal. Anyway, are you suggesting fdatasync to act as a destructive operation? -- Michal Hocko SUSE Labs