From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: squashfs-devel@lists.sourceforge.net,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Squashfs mainlining status?
Date: Wed, 04 Jun 2008 04:16:22 +0100 [thread overview]
Message-ID: <48460906.2080205@lougher.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0806021650190.28709@vixen.sonytel.be>
Geert Uytterhoeven wrote:
> Hi Phillip,
>
> I was wondering what's the status of mainlining squashfs?
> Is there anything I can do to help?
>
I am currently working on this. A re-write and merge of the Squashfs
metadata and fragment cache code has been finished (it is in the
Squashfs CVS tree). The original implementation had a number of
performance issues which I wanted to address before resubmission.
The major work of course is the move to a little endian layout without
any bit fields in the structures to make it easier to swap member fields
on big-endian architectures. I'm currently working on this on a non-CVS
branch. Most of the work till now has been without any attempt to
retain backwards compatibility with the current 3.3 little-endian
filesystem layout. After your private email regarding retaining
backwards compatibility I will look again at this issue, it may well be
that I will abandon my current layout changes that I have so far made.
I have taken time off work to work on the necessary mainline changes
full time (unpaid unfortunately, so I need to look for another job
soon). Hopefully this will mean I will make better progress than I have
been able to in the last couple of years.
Phillip
next prev parent reply other threads:[~2008-06-04 3:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 15:33 Squashfs mainlining status? Geert Uytterhoeven
2008-06-04 3:16 ` Phillip Lougher [this message]
2008-06-04 9:37 ` [Squashfs-devel] " Peter Korsgaard
2008-07-17 15:35 ` Geert Uytterhoeven
2008-07-17 15:47 ` Robert Lougher
2008-07-18 6:14 ` Geert Uytterhoeven
2008-07-18 12:37 ` Robert 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=48460906.2080205@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=squashfs-devel@lists.sourceforge.net \
/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