From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
anup@brainfault.org, ajones@ventanamicro.com,
Paul Walmsley <paul.walmsley@sifive.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
Alistair Francis <Alistair.Francis@wdc.com>,
apatel@ventanamicro.com, atishp@atishpatra.org,
jrtc27@jrtc27.com, rick@andestech.com, ycliang@andestech.com,
linux-riscv@lists.infradead.org, qemu-riscv@nongnu.org,
u-boot@lists.denx.de, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dt-bindings: riscv: deprecate riscv,isa
Date: Thu, 18 May 2023 18:06:24 +0100 [thread overview]
Message-ID: <20230518-elective-mossy-1bf147f5e9b8@spud> (raw)
In-Reply-To: <mhng-95b99ff5-9024-4672-bb84-7599f7a05129@palmer-ri-x1c9>
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
On Thu, May 18, 2023 at 07:41:17AM -0700, Palmer Dabbelt wrote:
> On Thu, 18 May 2023 07:06:17 PDT (-0700), Conor Dooley wrote:
> > On Thu, May 18, 2023 at 07:13:15PM +0530, Anup Patel wrote:
> > > On Thu, May 18, 2023 at 4:02 PM Andrew Jones <ajones@ventanamicro.com> wrote:
> > > > On Thu, May 18, 2023 at 09:58:30AM +0100, Conor Dooley wrote:
> > > One downside of this new approach is it will increase the size of DTB.
> > > Imaging 50 such DT properties in 46 CPU DT nodes.
> >
> > I should do a comparison between 50 extensions in riscv,isa and doing
> > this 50 times and see what the sizes are.
>
> I'm not sure how sensitive people are to DT size (presumably it'd be DTB
> size)?
>
> It's also not clear what we can do about it: RISC-V has lots of extensions,
> that's going to take encoding space. Sticking with an ambiguous encoding
> because it's smaller seems like a way to get burned in the long run.
I did actually go an look at this. I cheated a little and renamed the
properties to "riscv,isa-ext-foo", which is about as communicative IMO
as the longer name I currently have, but may seem more agreeable to the
size conscious.
I added 30 cpu nodes to mpfs.dtsi, each with 100 extensions of 6 chars
long. With just the string, containing "rv64imafdc_zabcde_...", it was
unreadable, but "only" took up 46k.
I then removed the multiletter extensions from riscv,isa & switched to
riscv,isa-base & 100 booleans. IMO it was more readable (although still
quite bad!), but took up 62k.
Removing all of the boolean properties, leaving me with 30 addtional harts
with "rv64imafdc" only, was 26k.
I think the generic limit for dtb files is 2 MiB? To me the size
increase doesn't sound like a bit problem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-18 17:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 8:58 [PATCH v1] dt-bindings: riscv: deprecate riscv,isa Conor Dooley
2023-05-18 10:31 ` Andrew Jones
2023-05-18 11:15 ` Conor Dooley
2023-05-18 11:25 ` Conor Dooley
2023-05-18 13:43 ` Anup Patel
2023-05-18 14:06 ` Conor Dooley
2023-05-18 14:41 ` Palmer Dabbelt
2023-05-18 17:06 ` Conor Dooley [this message]
2023-05-18 18:30 ` Sean Anderson
2023-05-18 21:42 ` Conor Dooley
2023-05-30 14:12 ` Conor Dooley
2023-06-08 19:15 ` Rob Herring
2023-06-08 19:30 ` Conor Dooley
2023-06-12 21:23 ` Conor Dooley
2023-06-13 13:28 ` Rob Herring
2023-06-13 14:11 ` Conor Dooley
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=20230518-elective-mossy-1bf147f5e9b8@spud \
--to=conor@kernel.org \
--cc=Alistair.Francis@wdc.com \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jrtc27@jrtc27.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=qemu-riscv@nongnu.org \
--cc=rick@andestech.com \
--cc=robh+dt@kernel.org \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.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