From: "Jared Hulbert" <jaredeh@gmail.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Advanced XIP File System
Date: Wed, 3 May 2006 08:58:36 -0700 [thread overview]
Message-ID: <6934efce0605030858k3967489p55ef98a26e71b761@mail.gmail.com> (raw)
In-Reply-To: <20060503154700.GD5250@wohnheim.fh-wedel.de>
> Correct. It is not a must-fix, but having seperate workspaces for all
> the filesystems seems wasteful.
Agreed. So we copy the cramfs uncompress routines line for line.
That optimization seems like low hanging fruit.
To consolidate them how should that be approached? Create
fs/uncompress.c? Modify axfs and cramfs to use it?
next prev parent reply other threads:[~2006-05-03 15:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 21:53 Jared Hulbert
2006-05-03 0:00 ` Arnd Bergmann
2006-05-03 1:59 ` Jared Hulbert
2006-05-03 2:27 ` Josh Boyer
2006-05-03 5:04 ` Jared Hulbert
2006-05-03 8:31 ` David Woodhouse
2006-05-03 19:14 ` Pavel Machek
2006-05-04 16:32 ` Jared Hulbert
2006-05-03 0:56 ` Josh Boyer
2006-05-03 3:17 ` Nicolas Pitre
2006-05-03 10:41 ` Josh Boyer
2006-05-03 12:11 ` David Woodhouse
2006-05-03 15:45 ` Jared Hulbert
2006-05-03 15:52 ` David Woodhouse
2006-05-03 15:57 ` Nicolas Pitre
2006-05-03 16:01 ` David Woodhouse
2006-05-03 16:10 ` Nicolas Pitre
2006-05-03 5:11 ` Jared Hulbert
2006-05-03 12:50 ` Mark Lord
2006-05-03 15:33 ` Jared Hulbert
2006-05-03 13:05 ` Jörn Engel
2006-05-03 15:31 ` Jared Hulbert
2006-05-03 15:47 ` Jörn Engel
2006-05-03 15:58 ` Jared Hulbert [this message]
2006-05-03 17:03 ` Jörn Engel
2006-05-03 18:58 ` Jared Hulbert
2006-05-03 16:38 ` Jan Engelhardt
2006-05-03 18:54 ` Jared Hulbert
2006-05-03 23:17 ` Josh Boyer
2006-05-03 23:48 ` Jared Hulbert
2006-05-04 0:21 ` Josh Boyer
2006-05-03 22:49 ` David Woodhouse
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=6934efce0605030858k3967489p55ef98a26e71b761@mail.gmail.com \
--to=jaredeh@gmail.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®