From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
Cc: <linux-kernel@vger.kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>,
Sai Prakash Ranjan <quic_saipraka@quicinc.com>,
Sibi Sankar <quic_sibis@quicinc.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>
Subject: Re: [PATCH V0 1/1] bootconfig: Increase max size of bootconfig from 32 KB to 256 KB for DCC support
Date: Tue, 10 Jan 2023 00:18:20 +0900 [thread overview]
Message-ID: <20230110001820.5ca81344286f614ed4ccec77@kernel.org> (raw)
In-Reply-To: <654357bcbfd3974072a558c494a51edafaa73e1a.1673261071.git.quic_schowdhu@quicinc.com>
On Mon, 9 Jan 2023 20:01:05 +0530
Souradeep Chowdhury <quic_schowdhu@quicinc.com> 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 <quic_schowdhu@quicinc.com>
> ---
> 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) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-01-09 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 14:31 [PATCH V0 0/1] bootconfig: Increase size and node limit of bootconfig for DCC support Souradeep Chowdhury
2023-01-09 14:31 ` [PATCH V0 1/1] bootconfig: Increase max size of bootconfig from 32 KB to 256 KB " Souradeep Chowdhury
2023-01-09 15:09 ` Bjorn Andersson
2023-01-10 10:57 ` Souradeep Chowdhury
2023-01-09 15:18 ` Masami Hiramatsu [this message]
2023-01-10 11:56 ` Souradeep Chowdhury
2023-01-10 14:46 ` Masami Hiramatsu
2023-01-10 15:08 ` Souradeep Chowdhury
2023-01-12 7:01 ` Masami Hiramatsu
2023-01-19 16:51 ` Souradeep Chowdhury
2023-01-19 23:37 ` Masami Hiramatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230110001820.5ca81344286f614ed4ccec77@kernel.org \
--to=mhiramat@kernel.org \
--cc=andersson@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_rjendra@quicinc.com \
--cc=quic_saipraka@quicinc.com \
--cc=quic_schowdhu@quicinc.com \
--cc=quic_sibis@quicinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).