Openembedded Core Discussions
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Ross Burton <Ross.Burton@arm.com>
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 12:38:37 +0100	[thread overview]
Message-ID: <9743d278bf2ccbff92436ccd30335a5f59a47b2b.camel@linuxfoundation.org> (raw)
In-Reply-To: <D6B1AC00-90EC-49C2-B66F-3849A46B010C@arm.com>

On Wed, 2022-05-25 at 10:34 +0000, Ross Burton wrote:
> > 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.

My worry is that it changes the task checksums for the native tools and
means the BSP can never be YP Compat.

> 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].

If the zaurus moved to ubifs, there is probably less of an issue and
just the kernel boot time remains but I'd hope zstd is being used there
too now (or will be).

Cheers,

Richard



  reply	other threads:[~2022-05-25 11:38 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
2022-05-25 11:38       ` richard.purdie [this message]
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=9743d278bf2ccbff92436ccd30335a5f59a47b2b.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Ross.Burton@arm.com \
    --cc=nd@arm.com \
    --cc=openembedded-core@lists.openembedded.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