Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp1683269pxu; Sun, 6 Dec 2020 03:58:59 -0800 (PST) X-Google-Smtp-Source: ABdhPJwKQJU+JcH90oJP9PMaVwa0Aq9QgewIE8gDhzxg2ie4FwTBImd6zBo51sal2bpE9cnaWEBO X-Received: by 2002:aa7:c84c:: with SMTP id g12mr2247362edt.193.1607255939189; Sun, 06 Dec 2020 03:58:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607255939; cv=none; d=google.com; s=arc-20160816; b=lzTf+xdheOFN/mAOujyUxEE4kRl4S7THc5yUd/JuhRmgkO3yIsGbexX9u96pwC+SNe gdJvzJGqNaCesgrzYW2jgl5mTlO6TdvTy8p/4Js6g9znuTS/5XEVDBnS2jkJMgq8iRlv UIwUDLn3+WHnkckbWLZjjtE6dA2IL12dXhpdc/tQcHyoAacXfkRi1uwhQ3t0OrF/wNrX IWAmN2Z1iiiDYeLeWi1hrV6ft+j/w1bA7fbxA0Wz6OVM+FAxw12f+WwuVADY8FJ3C8la ftI41GqRx2/c5aDDczMFEivqjb2xgEBkd/0YNc9HLQoytb6x7hpR3DeXlt52P/j+i9Pq FjrA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:dkim-signature:date; bh=eoHzXXijWlozq34Gyh/cHOCPFUE8IS/AkDsF2owcKfI=; b=WH/nWOtXZTHcOfN2naJA+qrNEDskT2Lqwk4V+lunlFU+MaKIOi21YTzU1cbxCjZYiD DqpALx61gyHXwNhWiV1Yjem7P1CU2BPYG13joVuwZ2Lm6X/pphfdi3xFa6OapnSmy8dM GQMbjMb/MTPBPvTMtNFzHtEytIPmxKLsvfPTHAPgdO0eet38Pl80PDNnGpZZiRGQwuET wFbsjcpE5PqtRGt+88UA3vekh+zLDLO3vqfPdO1idIhtCR3P6HHGzR17rzIyrDqgUiK8 yhz/2hF/f2XFIiShxGABsXzTbCZohPh9lkkR4nx4g2jYfOIM3OaGNncpiirozNFhGs3l zjpg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b="RXZ0B/nz"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id by23si4466731ejb.165.2020.12.06.03.58.36; Sun, 06 Dec 2020 03:58:59 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=k20201202 header.b="RXZ0B/nz"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727534AbgLFL4D (ORCPT + 99 others); Sun, 6 Dec 2020 06:56:03 -0500 Received: from mail.kernel.org ([198.145.29.99]:52020 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725767AbgLFL4D (ORCPT ); Sun, 6 Dec 2020 06:56:03 -0500 Date: Sun, 6 Dec 2020 13:55:17 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1607255723; bh=pTpsXS9CBriukmpy9E70AdN9gCV7E3J/symznTMEUrg=; h=From:To:Cc:Subject:References:In-Reply-To:From; b=RXZ0B/nzOzWsaFVRvI6ZjRbJ6wLRT2dJpYT4Dt7VBca4QCoJuM5SAZWP1N9Pu/zwP L0kazA7TFH12wCnfSkkCxQTRejZRN8sxziNtu3cB7pIooUdr68wQNcKzu54/fLE5zu xnwwI8rDDYJtXoAFUd/xAh6zMjUP65QQ1iibZRGBVu0IejhJOk+5a9T5MYS+Iq2tq2 LvLFHCJWkIYU2MhLSN7IH7KJ8FC2fSJFiDiuhmU371o+pDxHUv8Z6uhPNWeqXyu2qR lXPXaJio9ZOXl85oNHrlnop5TKKk/ADvXD+jDklROb25kQ8o30K/7mtfnMe3MtzZKE ZrP/4TuXtqjxg== From: Mike Rapoport To: carver4lio@163.com Cc: akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Hailong Liu Subject: Re: [PATCH] mm/memblock:use a more appropriate order calculation when free memblock pages Message-ID: <20201206115517.GL751215@kernel.org> References: <20201203152311.5272-1-carver4lio@163.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201203152311.5272-1-carver4lio@163.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 03, 2020 at 11:23:10PM +0800, carver4lio@163.com wrote: > From: Hailong Liu > > When system in the booting stage, pages span from [start, end] of a memblock > are freed to buddy in a order as large as possible (less than MAX_ORDER) at > first, then decrease gradually to a proper order(less than end) in a loop. > > However, *min(MAX_ORDER - 1UL, __ffs(start))* can not get the largest order > in some cases. Do you have examples? What is the memory configration that casues suboptimal order selection and what is the order in this case? > Instead, *__ffs(end - start)* may be more appropriate and meaningful. As several people reported using __ffs(end - start) is not correct. If the order selection is indeed suboptimal we'd need some better formula ;-) > Signed-off-by: Hailong Liu > --- > mm/memblock.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/mm/memblock.c b/mm/memblock.c > index b68ee8678..7c6d0dde7 100644 > --- a/mm/memblock.c > +++ b/mm/memblock.c > @@ -1931,7 +1931,7 @@ static void __init __free_pages_memory(unsigned long start, unsigned long end) > int order; > > while (start < end) { > - order = min(MAX_ORDER - 1UL, __ffs(start)); > + order = min(MAX_ORDER - 1UL, __ffs(end - start)); > > while (start + (1UL << order) > end) > order--; > -- > 2.17.1 > > -- Sincerely yours, Mike.