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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9ABABC54EBD for ; Mon, 9 Jan 2023 15:19:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Mime-Version:References:In-Reply-To: Message-Id:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=H7lxlrh9Oevsu5fj1HK/fuiHueJYTbAbnpEfi0GrqqM=; b=FGr+Z/1e1XH7a4 eFkPuHNNY7QK75FOXV4hO1OF2cFOcL+0NPKwlQY7A8Zkmz75AeaScPe2uT/c9qEFtzwpEi4VWNX1y JeJvJx8IRKOvUdpmWAdF464mNtM3nDi862CUZ9uRaQg7P0Em/zd6OxxuECy3R+4RY8FlAwCj1e+4M co1VOVLdwa2vtbBCD9+pZPKHKj09EvVaRBgPAcMqj443captevxx9eV6+2IrjVZ6/ne/gh8BluM+4 m8JD8bkTkwWJofUOC1D6JVeL9pX+rNKxvVp6VncBPM54evcYinQc7DMHZa7HF5jX01wLW0uUCxnbN AGS647dNrS+mrpuTZlBw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pEtv3-002BSf-LV; Mon, 09 Jan 2023 15:18:38 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pEtuu-002BPv-Eg for linux-arm-kernel@lists.infradead.org; Mon, 09 Jan 2023 15:18:29 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 3029DB80DEC; Mon, 9 Jan 2023 15:18:26 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D53CFC433EF; Mon, 9 Jan 2023 15:18:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1673277504; bh=VoylUKB7KAYjI4lL3TSlxJQLlRd4PyTwQaGlgfA/DY8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=So1ahHLTI2eUVOFZ4EDGcN1PG4A7gKafxwRPkrGQPA4DtaHIfcFLO5B/kPXwOuCQO OAxLK9ggU780vNJWdfmyQ5sB0tFoof8M7eVGC9QHasamgVwhFlU138IBQ0bKpHksZj Y/xRGLmdwdf8BB8BN8OwlLGCNVz7M9JhBdIzYTPAhjvzbNFKUZ/W+OcoDFgLbdwPLd gLUmN0ppSKJFXaKAPZZBwuL2Jtg7wOm01Wyw/rSe1NpEybxYD757dIi9wJ40HhWZlT GV5vvobXiziKnipDgmAsYqpmQhYVn04FwF6INf+FDPLZcwaozfLGlMcm6DipsP6At3 HqHr/OJQDJ4wA== Date: Tue, 10 Jan 2023 00:18:20 +0900 From: Masami Hiramatsu (Google) To: Souradeep Chowdhury Cc: , Bjorn Andersson , , , Sai Prakash Ranjan , Sibi Sankar , Rajendra Nayak Subject: Re: [PATCH V0 1/1] bootconfig: Increase max size of bootconfig from 32 KB to 256 KB for DCC support Message-Id: <20230110001820.5ca81344286f614ed4ccec77@kernel.org> In-Reply-To: <654357bcbfd3974072a558c494a51edafaa73e1a.1673261071.git.quic_schowdhu@quicinc.com> References: <654357bcbfd3974072a558c494a51edafaa73e1a.1673261071.git.quic_schowdhu@quicinc.com> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230109_071828_690134_B7B81D87 X-CRM114-Status: GOOD ( 19.50 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, 9 Jan 2023 20:01:05 +0530 Souradeep Chowdhury wrote: > Increasing the memory size of bootconfig to be able to handle a max number of > 8192 nodes to be fitted in memory size of 256KB. Sorry, but you missed the 'xbc_node::data' stores the index of the data and that is uint16_t. So the XBC_DATA_MAX is fixed limitation. The number of nodes (XBC_NODE_MAX) can be expanded because I just decided it to keep the pre-compiled array size ~8KB. Maybe expanding it to 64KB just increase the size of kernel on init memory (and freed after boot). Could you tell me why you need such a big data for your DCC? Thank you, > > Signed-off-by: Souradeep Chowdhury > --- > include/linux/bootconfig.h | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/include/linux/bootconfig.h b/include/linux/bootconfig.h > index 1611f9d..64d233b 100644 > --- a/include/linux/bootconfig.h > +++ b/include/linux/bootconfig.h > @@ -55,11 +55,11 @@ struct xbc_node { > } __attribute__ ((__packed__)); > > #define XBC_KEY 0 > -#define XBC_VALUE (1 << 15) > -/* Maximum size of boot config is 32KB - 1 */ > +#define XBC_VALUE (1 << 18) > +/* Maximum size of boot config is 256KB - 1 */ > #define XBC_DATA_MAX (XBC_VALUE - 1) > > -#define XBC_NODE_MAX 1024 > +#define XBC_NODE_MAX 8192 > #define XBC_KEYLEN_MAX 256 > #define XBC_DEPTH_MAX 16 > > -- > 2.7.4 > -- Masami Hiramatsu (Google) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel