From: Ross Burton <Ross.Burton@arm.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
nd <nd@arm.com>
Subject: Re: [OE-core] [PATCH 3/9] mtd-utils: disable LZO by default
Date: Wed, 25 May 2022 10:34:22 +0000 [thread overview]
Message-ID: <D6B1AC00-90EC-49C2-B66F-3849A46B010C@arm.com> (raw)
In-Reply-To: <6585ba44a9ef9dd9ef8c0d70ac570f97d8e24bb2.camel@linuxfoundation.org>
> This and kernel compression are the two pieces that worry me a little.
> LZO is still probably one of the best speed/size compromises and was
> the reason it was added to jffs2. I'm not sure there are many devices
> that still use flash directly via jffs2 but this probably still does
> have a use there. Obviously it would still be in meta-oe but I'm
> worried the "off by default" will catch out a few old BSPs and be a
> pain to enable. At lot of this history was paged out in long term
> storage!
Enabling should just be a matter of pulling in meta-oe and flipping the packageconfigs, so I don’t see this as a huge problem.
Looking in the time machine that is meta-handheld, I see the zaurus machines turn on LZO in the JFFS2 kernel module, but they also build UBIFS images which explicitly use zlib instead of lzo. UBIFS also support Zstd now, so that’s probably a better option all around: it compresses almost as well as zlib but almost as fast as lzo[1].
Ross
[1] from btrfs benchmarks at https://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git/commit/?h=next&id=5c1aab1dd5445ed8bdcdbb575abc1b0d7ee5b2e7
next prev parent reply other threads:[~2022-05-25 10:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 15:23 [PATCH 1/9] lzo: Add further info to a patch Ross Burton
2022-05-24 15:23 ` [PATCH 2/9] btrfs-tools: add a PACKAGECONFIG for lzo Ross Burton
2022-05-24 15:23 ` [PATCH 3/9] mtd-utils: disable LZO by default Ross Burton
2022-05-25 9:33 ` [OE-core] " richard.purdie
2022-05-25 10:34 ` Ross Burton [this message]
2022-05-25 11:38 ` richard.purdie
2022-05-24 15:23 ` [PATCH 4/9] squashfs-tools: " Ross Burton
2022-05-24 15:23 ` [PATCH 5/9] libarchive: " Ross Burton
2022-05-24 15:23 ` [PATCH 6/9] lzop: remove recipe from oe-core Ross Burton
2022-05-24 15:23 ` [PATCH 7/9] oeqa/selftest/imagefeatures: don't exercise lzo compression Ross Burton
2022-05-24 15:24 ` [PATCH 8/9] packagegroup-self-hosted: remove lzo Ross Burton
2022-05-24 15:24 ` [PATCH 9/9] lzo: remove recipe from oe-core Ross Burton
2022-05-25 8:03 ` [OE-core] " Luca Ceresoli
2022-05-25 11:26 ` Ross Burton
2022-05-25 12:59 ` Bruce Ashfield
2022-05-25 13:45 ` Ross Burton
2022-05-25 13:55 ` Bruce Ashfield
2022-05-25 8:00 ` [OE-core] [PATCH 1/9] lzo: Add further info to a patch Luca Ceresoli
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=D6B1AC00-90EC-49C2-B66F-3849A46B010C@arm.com \
--to=ross.burton@arm.com \
--cc=nd@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.