Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp1396105pxx; Fri, 30 Oct 2020 09:02:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwanGt+D/8A1tjLbdsQCe9fjbC+HxZ/XTCLP2MdGpHku962WV+IoNuk0a76o6LrdsovRybf X-Received: by 2002:a19:c786:: with SMTP id x128mr1168466lff.478.1604073768437; Fri, 30 Oct 2020 09:02:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1604073768; cv=none; d=google.com; s=arc-20160816; b=s6PRacntlRqI8fELmtR3OlHoruJ19zuRR/CqDwEfAh83n6L7wIcK/O3aEogUFo5jRO Is2l/7kooXRPV0B/rKLnNsRoJSAF8u2CoxGI6KNGHisjuxWmtQ/Ap05I7nxkiLZ2Z/PN Sbp2SSQUsxATC8Ry9AtSciEQgQLL818RsMtgcOLIOqETIT/KE1lwq5WApBX5OlhYsq4q SO1bsQxtmJMiH0VeCVY3G2qqEiS0efaXykzp58cv2JJ9BuE6VUWtZ61UOY2CrNFw7fjc IMB1BVyqKarhMPvXUKMh7fxeQWb3tVUocT437QFrJ7UgskqH9Caet0IdxK4jv2XJXDWy VUSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=N8VKWkJD00t1aYWYq8dibXLUTEDm5BtMu4o13QJHCEo=; b=Cdqy9sFNqOdEwqYoMBucxcOqeRa/1jvMxXN+8zZxs6X7UDDRnfTqXprTSmQ0x2evnW 7t4qa3Q3wdrzuWvMWP1glTMmTy1vRcLd2pCdDBjj4yJ1ZHpQVzH8oiulg8xXFz7RxXRP Rof01sjO+sjdTvFY202CNKewMd0MNh1X9VgXbheFNdySIWIQFyTdljos0XoRA238zD/3 qzhjwnlySGb7XJlN4Zx+ab8QpqqLOHjQfeLHEPi8E+cngiwzKpYCT1yjoEaStFfRRFq5 VsAwAA946V5nYI7wS1fDh6NozCuiKKH6yWDCq5Usvm3CeUKXzo73SRLz1wAguOPgsYNL 3a7g== 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 a26si3263700ljm.83.2020.10.30.09.02.20; Fri, 30 Oct 2020 09:02:48 -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 S1726662AbgJ3QAV (ORCPT + 99 others); Fri, 30 Oct 2020 12:00:21 -0400 Received: from mx3.molgen.mpg.de ([141.14.17.11]:34631 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726120AbgJ3QAV (ORCPT ); Fri, 30 Oct 2020 12:00:21 -0400 Received: from [192.168.0.2] (ip5f5af1ae.dynamic.kabel-deutschland.de [95.90.241.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id C1CC220646217; Fri, 30 Oct 2020 17:00:18 +0100 (CET) Subject: Re: [PATCH v2 1/2] init/Kconfig: Fix CPU number in LOG_CPU_MAX_BUF_SHIFT description To: Petr Mladek , Sergey Senozhatsky Cc: "Luis R . Rodriguez" , linux-kernel@vger.kernel.org References: <20200811092924.6256-1-pmenzel@molgen.mpg.de> From: Paul Menzel Message-ID: Date: Fri, 30 Oct 2020 17:00:18 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: <20200811092924.6256-1-pmenzel@molgen.mpg.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Petr, Am 11.08.20 um 11:29 schrieb Paul Menzel: > Currently, LOG_BUF_SHIFT defaults to 17, which is 2 ^ 17 bytes = 128 KB, > and LOG_CPU_MAX_BUF_SHIFT defaults to 12, which is 2 ^ 12 bytes = 4 KB. > > Half of 128 KB is 64 KB, so more than 16 CPUs are required for the value > to be used, as then the sum of contributions is greater than 64 KB for > the first time. My guess is, that the description was written with the > configuration values used in the SUSE in mind. > > Fixes: 23b2899f7f ("printk: allow increasing the ring buffer depending on the number of CPUs") > Cc: Luis R. Rodriguez > Cc: linux-kernel@vger.kernel.org > Reviewed-by: Petr Mladek > Signed-off-by: Paul Menzel > --- > v2: Add Reviewed-by tag > > init/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/init/Kconfig b/init/Kconfig > index d6a0b31b13dc..9dc607e3806f 100644 > --- a/init/Kconfig > +++ b/init/Kconfig > @@ -718,7 +718,7 @@ config LOG_CPU_MAX_BUF_SHIFT > with more CPUs. Therefore this value is used only when the sum of > contributions is greater than the half of the default kernel ring > buffer as defined by LOG_BUF_SHIFT. The default values are set > - so that more than 64 CPUs are needed to trigger the allocation. > + so that more than 16 CPUs are needed to trigger the allocation. > > Also this option is ignored when "log_buf_len" kernel parameter is > used as it forces an exact (power of two) size of the ring buffer. Could you please apply this trivial patch from the two patches already, so I do not have to resend it? Kind regards, Paul