From: Peter Korsgaard <jacmet@sunsite.dk>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
squashfs-devel@lists.sourceforge.net,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [Squashfs-devel] Squashfs mainlining status?
Date: Wed, 04 Jun 2008 11:37:34 +0200 [thread overview]
Message-ID: <87od6h7d7l.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <48460906.2080205@lougher.demon.co.uk> (Phillip Lougher's message of "Wed\, 04 Jun 2008 04\:16\:22 +0100")
>>>>> "Phillip" == Phillip Lougher <phillip@lougher.demon.co.uk> writes:
Hi,
Phillip> I am currently working on this. A re-write and merge of the
Phillip> Squashfs metadata and fragment cache code has been finished
Phillip> (it is in the Squashfs CVS tree). The original
Phillip> implementation had a number of performance issues which I
Phillip> wanted to address before resubmission.
Nice to hear! Are you aiming for 2.6.27 or later?
Phillip> The major work of course is the move to a little endian
Phillip> layout without any bit fields in the structures to make it
Phillip> easier to swap member fields on big-endian architectures.
Phillip> I'm currently working on this on a non-CVS branch.
Phillip> Most of the work till now has been without any attempt to
Phillip> retain backwards compatibility with the current 3.3
Phillip> little-endian filesystem layout. After your private email
Phillip> regarding retaining backwards compatibility I will look
Phillip> again at this issue, it may well be that I will abandon my
Phillip> current layout changes that I have so far made.
What private mail? Anything of interest to the rest of the group? As I
said earlier, I'm strongly in faviour of cleaning up the layout now
and get rid of all the backwards compatibility code. Doing it once
it's in mainline will be really hard.
Phillip> I have taken time off work to work on the necessary mainline
Phillip> changes full time (unpaid unfortunately, so I need to look
Phillip> for another job soon). Hopefully this will mean I will make
Phillip> better progress than I have been able to in the last couple
Phillip> of years.
;) Good luck with it. Is there anything I can do to help?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-06-04 9:37 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
2008-06-04 9:37 ` Peter Korsgaard [this message]
2008-07-17 15:35 ` [Squashfs-devel] " 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=87od6h7d7l.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
--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