From: "H. Peter Anvin" <hpa@zytor.com>
To: quinlan@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cramfs big-endian kernel patch
Date: Mon, 25 Feb 2002 17:25:30 -0800 [thread overview]
Message-ID: <200202260127.RAA01938@cesium.transmeta.com> (raw)
In-Reply-To: <15482.53400.786310.950430@sodium.transmeta.com>
In article <15482.53400.786310.950430@sodium.transmeta.com> of
linux.dev.kernel, you write:
>
> +Currently, cramfs can be read only by kernels with PAGE_CACHE_SIZE ==
> +4096. This is a bug, but it hasn't been decided what the best fix is.
> +For the moment if you have larger pages you can just change the
> +#define in mkcramfs.c, so long as you don't mind the filesystem
> +becoming unreadable to future kernels.
>
For the binary format to be compatible, there is only one solution: if
PAGE_CACHE_SIZE > 4096, you decompress more than one cramfs chunk into
the same page.
If the binary format can change, then you could implement the same
solution used in zisofs.
FWIW, currently on Linux I believe:
4096 <= PAGE_CACHE_SIZE <= 32768
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
prev parent reply other threads:[~2002-02-26 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 0:02 [PATCH] cramfs big-endian kernel patch Daniel Quinlan
2002-02-26 1:25 ` H. Peter Anvin [this message]
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=200202260127.RAA01938@cesium.transmeta.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quinlan@transmeta.com \
/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