From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] dracut: lower ram usage at commpression
Date: Wed, 17 May 2023 08:49:27 +0100 [thread overview]
Message-ID: <11D5DC2E-E922-4719-A031-870A51AA3466@ipfire.org> (raw)
In-Reply-To: <20230516090606.1170-1-arne_f@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
Thank you for this patch. Please go ahead and merge it straight into next.
However, I would like to put on the record that I generally disagree with optimising things for the lowest common denominator. It will not allow us to take advantage of modern features whether that is in hardware or software, so let’s aim to avoid hacks like this whenever possible in the future.
Best,
-Michael
> On 16 May 2023, at 10:06, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
>
> this lower the compression ratio sligtly (the ramdlisk is 100kb
> larger) and use only a single thread now. (it's still faster than
> before on a dual core.)
>
> Note to Peter: if there are no other changes on dracut ship only
> /usr/lib/dracut/dracut.conf.d/ipfire.conf
> at core update.
>
> fixes: #13091
>
> Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
> ---
> config/dracut/ipfire.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/config/dracut/ipfire.conf b/config/dracut/ipfire.conf
> index bab5c8a2e..5a4f0aa7c 100644
> --- a/config/dracut/ipfire.conf
> +++ b/config/dracut/ipfire.conf
> @@ -2,4 +2,4 @@
> early_microcode="yes"
>
> # Compress using Zstandard
> -compress="zstd"
> +compress="zstd -10 -q -T1"
> --
> 2.34.1
>
prev parent reply other threads:[~2023-05-17 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 9:06 Arne Fitzenreiter
2023-05-17 7:49 ` Michael Tremer [this message]
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=11D5DC2E-E922-4719-A031-870A51AA3466@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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