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=-5.8 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 2D0AFC433DB for ; Wed, 17 Feb 2021 07:57:14 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id A257664E3E for ; Wed, 17 Feb 2021 07:57:13 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A257664E3E Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 1B86B8D0027; Wed, 17 Feb 2021 02:57:13 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 1691B8D0019; Wed, 17 Feb 2021 02:57:13 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 07F9F8D0027; Wed, 17 Feb 2021 02:57:13 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0208.hostedemail.com [216.40.44.208]) by kanga.kvack.org (Postfix) with ESMTP id E3BCD8D0019 for ; Wed, 17 Feb 2021 02:57:12 -0500 (EST) Received: from smtpin06.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id A0ADF180AD83A for ; Wed, 17 Feb 2021 07:57:12 +0000 (UTC) X-FDA: 77827004304.06.92C41EC Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf23.hostedemail.com (Postfix) with ESMTP id 0B0AFA0009C5 for ; Wed, 17 Feb 2021 07:57:11 +0000 (UTC) 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=1613548631; 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=cgmC7AaJ6yBPNg2oaCmQrFfiwgvCyyz07hRRATeOpLs=; b=To0WYKySQSp7O/XtbTiAzCmtGN5p62m1ojqofnnGbN7v8Fw7rVkBXzJl0T62ClkSmbVRov A6U4BBcabffv/szw+FagGMLxu/33iWy//1Frfu+EKHUWTHQ37MvnbQBbFdCnNqARGJx6JZ r7t4qd5VXzwTCqzFvzaRWe/8guyZ1Y4= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 016E6AFF1; Wed, 17 Feb 2021 07:57:11 +0000 (UTC) Date: Wed, 17 Feb 2021 08:57:09 +0100 From: Michal Hocko To: Mike Kravetz Cc: Eiichi Tsukata , corbet@lwn.net, mcgrof@kernel.org, keescook@chromium.org, yzaikin@google.com, akpm@linux-foundation.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, felipe.franciosi@nutanix.com Subject: Re: [RFC PATCH] mm, oom: introduce vm.sacrifice_hugepage_on_oom Message-ID: References: <20210216030713.79101-1-eiichi.tsukata@nutanix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: 0B0AFA0009C5 X-Stat-Signature: 1s3ti4wxe9upaskz43ii1eaby99xb9oq Received-SPF: none (suse.com>: No applicable sender policy available) receiver=imf23; identity=mailfrom; envelope-from=""; helo=mx2.suse.de; client-ip=195.135.220.15 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1613548631-835901 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 Tue 16-02-21 14:30:15, Mike Kravetz wrote: [...] > However, this is an 'opt in' feature. So, I would not expect anyone who > carefully plans the size of their hugetlb pool to enable such a feature. > If there is a use case where hugetlb pages are used in a non-essential > application, this might be of use. I would really like to hear about the specific usecase. Because it smells more like a misconfiguration. What would be non-essential hugetlb pages? This is not a resource to be pre-allocated just in case, right? -- Michal Hocko SUSE Labs