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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 60DF2C4332F for ; Tue, 11 Oct 2022 15:00:24 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id C81576B0071; Tue, 11 Oct 2022 11:00:23 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id C311A6B0073; Tue, 11 Oct 2022 11:00:23 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id B1F856B0074; Tue, 11 Oct 2022 11:00:23 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id A03956B0071 for ; Tue, 11 Oct 2022 11:00:23 -0400 (EDT) Received: from smtpin20.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 3C1B8405FD for ; Tue, 11 Oct 2022 15:00:23 +0000 (UTC) X-FDA: 80008979526.20.8565B58 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by imf03.hostedemail.com (Postfix) with ESMTP id 71FBC20032 for ; Tue, 11 Oct 2022 15:00:17 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 0D84A20121; Tue, 11 Oct 2022 15:00:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1665500416; h=from:from:reply-to: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=RO0FO74ctDC9cFYZEDLiw7BGFiXGuRuOlnU9ALUUx4Q=; b=UdX58LtbOBVnHrZvPxzq+OnrT4JBCxyKX7In8GNplrTy13057zqHjS17NhVXO+X6uvxB+F yWFaRqu7LeV7MI2FHa89kpRAGRakFbDpECYhA7UBIDylrvfmtmTE9wEJI6mhsWJfIxmD+O f+rcsieq2uSRQGfJSh//Jbj6k19Qu2A= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id C78AC139ED; Tue, 11 Oct 2022 15:00:15 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id fuh0LP+ERWNxSQAAMHmgww (envelope-from ); Tue, 11 Oct 2022 15:00:15 +0000 Date: Tue, 11 Oct 2022 17:00:14 +0200 From: Michal Hocko To: Frank van der Linden Cc: Zhongkun He , corbet@lwn.net, akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, linux-doc@vger.kernel.org, wuyun.abel@bytedance.com Subject: Re: [RFC] mm: add new syscall pidfd_set_mempolicy() Message-ID: References: <20221010094842.4123037-1-hezhongkun.hzk@bytedance.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1665500417; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=RO0FO74ctDC9cFYZEDLiw7BGFiXGuRuOlnU9ALUUx4Q=; b=1Cv5Rw3lEYd++yB08BgqoaGwzwNyHKnt3qOH0yQad0CpESpB2jR1/hmmbZm7OFRAfqEpue BSEmT/ZJyeGZ5f1yktRgJ/+jxUU19zkGnalEcr79IX2FTcxZTmDX/eXVWRsbtWVrO9pDXr 1u48TRc9y+xJIxFhw7ET64AzEwnVnDA= ARC-Authentication-Results: i=1; imf03.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=UdX58Ltb; spf=pass (imf03.hostedemail.com: domain of mhocko@suse.com designates 195.135.220.29 as permitted sender) smtp.mailfrom=mhocko@suse.com; dmarc=pass (policy=quarantine) header.from=suse.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1665500417; a=rsa-sha256; cv=none; b=y4+fAuDcBZC/pMR3FXSqzoni5cJgfHd3m+gXLGbDtVKeZXrFFdrO6TYF28b4dCxV5SxnDM C0GIuaVserOKA1JPPvMBRqqpnuhzkI9++zSMqL2FlkQ5dl0dU+sihJKIocyBuPTM0eTSl2 e2NCfsCEeKtdjG8U4yQv3ftAL8Qg4r0= Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=UdX58Ltb; spf=pass (imf03.hostedemail.com: domain of mhocko@suse.com designates 195.135.220.29 as permitted sender) smtp.mailfrom=mhocko@suse.com; dmarc=pass (policy=quarantine) header.from=suse.com X-Rspam-User: X-Rspamd-Server: rspam04 X-Stat-Signature: jkmntprhsnrq7nkyryem87gy3ydrjgmy X-Rspamd-Queue-Id: 71FBC20032 X-HE-Tag: 1665500417-286822 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon 10-10-22 09:22:13, Frank van der Linden wrote: > For consistency with process_madvise(), I would suggest calling it > process_set_mempolicy. This operation has per-thread rather than per-process semantic so I do not think your proposed naming is better. > Other than that, this makes sense. To complete > the set, perhaps a process_mbind() should be added as well. What do > you think? Is there any real usecase for this interface? How is the caller supposed to make per-range decisions without a very involved coordination with the target process? -- Michal Hocko SUSE Labs