Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp1086914ybh; Wed, 22 Jul 2020 23:19:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy7gjTBOqSUnHiKnNdjcsBvblK/d2EkbRzw7T6n0tiVKn+J8CmZoTjSGTTKWoDSm+5EIo+U X-Received: by 2002:a17:906:f907:: with SMTP id lc7mr3060737ejb.143.1595485167262; Wed, 22 Jul 2020 23:19:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595485167; cv=none; d=google.com; s=arc-20160816; b=l7HAq9NhciZsswqB8lKsa//YYKZIFdPSxDvp2xfAPS3wVZpHuim7CnJRMxEzG72kH4 d2cLLfbL52Me0vMmI5OsmZXygi+0x939PlgX84xlsbc40IAlbcRxSEpDOPoeJ3YjeFYx 474X58TrayFUlYR2GOCr19UDLknekf79YvT+uBidL3fpd8rq2pkjlA7iWdhhq6kmHZzc RuyEKLJspnoZeiRHHoq0sGXDY0Ac/7Gz39O38K8I7Dsc1fxxvUeZkBPbza7jO59huWqC /OywBLo9qvM5WDtsEwjzzdX/bfMWvyxLG1xnI5CeWTCk8WCGwtfNJGc5Y4w/kBhbhFtX c2UQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=QADSQZt6eA2ynAo602f0VKk2gTA/x5mizdY487pMD3A=; b=UFpey5ZGgJnzErzULqyJomLmwuGQl0Ei1gA9rixSNVvI2C3uXbvysJvt7U47F18aXp l0/ul+iKz/6YgQrIBDL08If+JfeOPbNENAQt3lpuTTOYRfSFrUpJ5d/vwWISluvm5i4Q J9Rye32JzFy+lySCI4SStIHyqO1lk0w9laPaJzb7EAwmOxad50BwyceAMJkMDqgAEYiY TXrfb5lLqNSQF2JsSN1OqMv9OGGO5qfLD3Ddqnnehi0cArYgcMLKykk0Tc801pmxmL0W DG6xMRJNAYTLCA+6E9N+Q2T6rWfTFDy8A1vdfvp1idqyquns4sHT8deWMqMuNWnuEAHH +ZtQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dk25si1305520edb.28.2020.07.22.23.19.04; Wed, 22 Jul 2020 23:19:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727769AbgGWGRC (ORCPT + 99 others); Thu, 23 Jul 2020 02:17:02 -0400 Received: from foss.arm.com ([217.140.110.172]:39672 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726522AbgGWGRC (ORCPT ); Thu, 23 Jul 2020 02:17:02 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A8F0730E; Wed, 22 Jul 2020 23:17:01 -0700 (PDT) Received: from [10.163.85.73] (unknown [10.163.85.73]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 78EB73F66E; Wed, 22 Jul 2020 23:16:59 -0700 (PDT) Subject: Re: [PATCH v2 4/4] mm/hugetl.c: warn out if expected count of huge pages adjustment is not achieved To: Baoquan He , linux-kernel@vger.kernel.org Cc: linux-mm@kvack.org, mike.kravetz@oracle.com, david@redhat.com, akpm@linux-foundation.org References: <20200723032248.24772-1-bhe@redhat.com> <20200723032248.24772-5-bhe@redhat.com> From: Anshuman Khandual Message-ID: <62c8ce6c-fe98-f371-99b6-cfdb96d1c2fd@arm.com> Date: Thu, 23 Jul 2020 11:46:30 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20200723032248.24772-5-bhe@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/23/2020 08:52 AM, Baoquan He wrote: > A customer complained that no message is logged wh en the number of > persistent huge pages is not changed to the exact value written to > the sysfs or proc nr_hugepages file. > > In the current code, a best effort is made to satisfy requests made > via the nr_hugepages file. However, requests may be only partially > satisfied. > > Log a message if the code was unsuccessful in fully satisfying a > request. This includes both increasing and decreasing the number > of persistent huge pages. But is kernel expected to warn for all such situations where the user requested resources could not be allocated completely ? Otherwise, it does not make sense to add an warning for just one such situation.