From: Jan Kiszka <jan.kiszka@siemens.com>
To: Srinuvasan Arjunan <srinuvasanasv@gmail.com>
Cc: srinuvasan.a@siemens.com, isar-users@googlegroups.com, ubely@ilbers.de
Subject: Re: [PATCH] recipes-initramfs/compress-initrd: add recipe to compress initrd with xz
Date: Mon, 13 May 2024 08:29:18 +0200 [thread overview]
Message-ID: <c149be49-5e1d-4793-b5c8-a7831bffff24@siemens.com> (raw)
In-Reply-To: <CAB2Z2nMbYtEMv6u1y+6ik2t-a-4n8iJiXZSQn3BuJrPn95mdUA@mail.gmail.com>
On 13.05.24 07:47, Srinuvasan Arjunan wrote:
>
>
> On Mon, May 13, 2024 at 10:57 AM 'Jan Kiszka' via isar-users
> <isar-users@googlegroups.com <mailto:isar-users@googlegroups.com>> wrote:
>
> On 13.05.24 07:26, srinuvasan.a@siemens.com
> <mailto:srinuvasan.a@siemens.com> wrote:
> > From: srinuvasan <srinuvasan.a@siemens.com
> <mailto:srinuvasan.a@siemens.com>>
> >
> > By default initrd compressed with zstd tool, with the present
> bullseye base image
> > of amd64 the initrd size is almost 27MB, this can be reduced with
> the help of xz tool,
> > using this one the generated initrd size is almost 18MB, we saved
> almost 9MB.
> >
>
> Isn't that just a matter of increasing the compression rate of zstd? It
> seems xz is getting out of fashion generally, and it comes with higher
> decompression load.
>
> Jan
>
>
> Sorry, its not zstd tool, the default one is gzip (wrongly captured in
> commit message), Just i pushed this patch for very limited memory
> requirement embedded devices, in this case i considered the memory
> requirement not a decompression load.
>
OK, but then not hard-code the tool used for compression, rather make it
configurable.
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-05-13 6:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 5:26 srinuvasan.a
2024-05-13 5:27 ` Jan Kiszka
2024-05-13 5:47 ` Srinuvasan Arjunan
2024-05-13 6:29 ` Jan Kiszka [this message]
2024-05-13 6:47 ` MOESSBAUER, Felix
2024-05-13 9:41 ` [PATCH v1] " srinuvasan.a
2024-05-30 5:49 ` Uladzimir Bely
2024-05-30 5:52 ` Srinuvasan Arjunan
2024-05-31 7:35 ` Jan Kiszka
2024-04-17 13:43 ` [PATCH V3] " srinuvasan.a
2024-07-08 9:44 ` Srinuvasan Arjunan
2024-07-18 11:36 ` Srinuvasan Arjunan
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=c149be49-5e1d-4793-b5c8-a7831bffff24@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=srinuvasan.a@siemens.com \
--cc=srinuvasanasv@gmail.com \
--cc=ubely@ilbers.de \
/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