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 45198C433DB for ; Wed, 17 Feb 2021 07:58:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DA6F764E4A for ; Wed, 17 Feb 2021 07:58:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231725AbhBQH6E (ORCPT ); Wed, 17 Feb 2021 02:58:04 -0500 Received: from mx2.suse.de ([195.135.220.15]:48850 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230145AbhBQH55 (ORCPT ); Wed, 17 Feb 2021 02:57:57 -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=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: Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org 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