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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6361CC4332F for ; Wed, 13 Oct 2021 14:26:32 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 0CDEB6113E for ; Wed, 13 Oct 2021 14:26:31 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 0CDEB6113E Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id 4C3296B006C; Wed, 13 Oct 2021 10:26:31 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 473096B0071; Wed, 13 Oct 2021 10:26:31 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 38A11900002; Wed, 13 Oct 2021 10:26:31 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0145.hostedemail.com [216.40.44.145]) by kanga.kvack.org (Postfix) with ESMTP id 2BDCB6B006C for ; Wed, 13 Oct 2021 10:26:31 -0400 (EDT) Received: from smtpin04.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id E105E18042E2A for ; Wed, 13 Oct 2021 14:26:30 +0000 (UTC) X-FDA: 78691639740.04.F5F64A4 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by imf12.hostedemail.com (Postfix) with ESMTP id 792AE10000AC for ; Wed, 13 Oct 2021 14:26:30 +0000 (UTC) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out1.suse.de (Postfix) with ESMTP id 714062195C; Wed, 13 Oct 2021 14:26:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1634135189; 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=1A37pVasNYvqmdWZyYR4EfMHZ9CZ5Wa9qMX6GgtqTNo=; b=K1oCyba59Wg7aWWCyLMF3fcKqETHd+3JKg0OFCyRqZfLKr2J1cWATnW82hLBVFh7J59dBo iFBU5yZWIGS58HHqb/iKfMckCQRtkVPaC4g2xTSSjHtxcHvtscTdga94D0bIMtSOFbA91k r3A3YAJRPjOLFecT+8Ws8V8+TyzI/6U= Received: from suse.cz (unknown [10.100.201.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 9E6AEA3B81; Wed, 13 Oct 2021 14:26:24 +0000 (UTC) Date: Wed, 13 Oct 2021 16:26:28 +0200 From: Michal Hocko To: "Aneesh Kumar K.V" Cc: linux-mm@kvack.org, akpm@linux-foundation.org, Ben Widawsky , Dave Hansen , Feng Tang , Andrea Arcangeli , Mel Gorman , Mike Kravetz , Randy Dunlap , Vlastimil Babka , Andi Kleen , Dan Williams , Huang Ying , linux-api@vger.kernel.org Subject: Re: [RFC PATCH] mm/mempolicy: add MPOL_PREFERRED_STRICT memory policy Message-ID: References: <20211013094539.962357-1-aneesh.kumar@linux.ibm.com> <4399a215-296f-e880-c5f4-8065ab13d210@linux.ibm.com> <9a0baa59-f316-103f-3030-990cd91d1813@linux.ibm.com> <291424a2-c962-533e-c755-e4239fd55f5d@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <291424a2-c962-533e-c755-e4239fd55f5d@linux.ibm.com> X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: 792AE10000AC X-Stat-Signature: urt9e6e9769iuogez5srctqatkb71y9c Authentication-Results: imf12.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=K1oCyba5; dmarc=pass (policy=quarantine) header.from=suse.com; spf=pass (imf12.hostedemail.com: domain of mhocko@suse.com designates 195.135.220.28 as permitted sender) smtp.mailfrom=mhocko@suse.com X-HE-Tag: 1634135190-225989 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 Wed 13-10-21 19:27:03, Aneesh Kumar K.V wrote: [...] > Another option is to keep this mbind(2) specific and overload flags to be > the preferred nodeid. > > mbind(va, len, MPOL_PREFERRED_STRICT, nodemask, max_node, preferred_node); First of all I do not think you really want to create a new memory policy for this. Not to mention that PREFERRED_STRICT is kinda weird in the first place but one could argue that a preference of the first node to try is not really specific to BIND/PREFERRED_MANY. Overloading flags is a nogo. -- Michal Hocko SUSE Labs