From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: linux-embedded <linux-embedded@vger.kernel.org>
Cc: Phillip Lougher <phillip@lougher.demon.co.uk>
Subject: Squashfs performance (3.3 vs 4.0 in mainline)
Date: Thu, 10 Dec 2009 15:02:43 +0100 [thread overview]
Message-ID: <20091210150243.2ed788f4@marrow.netinsight.se> (raw)
Hi!
I'm running 2.6.31 on a slow ARM platform and using squashfs 4.0 as
shipped with the kernel. It's a Sharp LH79524, so the architecture
itself isn't mainlined yet.
Squashfs works well, but I've noted a performance regression compared
to the out-of-tree squashfs 3.3 which we ran on 2.6.23. The new kernel
is faster until the squashfs root filesystem is mounted, but after that
it goes downhill. Especially mounting takes a lot more time with the
new:
2.6.23 / 3.3:
[ 0.01]: [ 1.250000] RAMDISK: squashfs filesystem found at block 0
[ 0.01]: [ 1.260000] RAMDISK: Loading 2156KiB [1 disk] into ram disk... done.
[ 1.39]: [ 2.650000] VFS: Mounted root (squashfs filesystem) readonly.
[ 0.01]: [ 2.660000] Freeing init memory: 80K
2.6.31 / 4.0:
[ 0.00]: [ 1.080000] RAMDISK: squashfs filesystem found at block 0
[ 0.01]: [ 1.090000] RAMDISK: Loading 2372KiB [1 disk] into ram disk... done.
[ 2.79]: [ 3.880000] VFS: Mounted root (squashfs filesystem) readonly on device 1:0.
[ 0.01]: [ 3.890000] Freeing init memory: 80K
(The first column is the time difference compared to last timestamp).
Are there any general changes which could have caused this difference?
I've tried with various mksquashfs options, and -noI makes it somewhat
faster (and larger), but not near the old version.
// Simon
next reply other threads:[~2009-12-10 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 14:02 Simon Kagstrom [this message]
2009-12-11 11:55 ` Squashfs performance (3.3 vs 4.0 in mainline) Phillip Lougher
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=20091210150243.2ed788f4@marrow.netinsight.se \
--to=simon.kagstrom@netinsight.net \
--cc=linux-embedded@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).