cramfs: support for other endianness
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 2 patches 12 repliesIn review
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] cramfs: update README file
This patch updates the readme file according to the new mount option "swapendian".
Signed-off-by Andi Drebes <[email protected]>
--- fs/cramfs/README | 21 +++++++++------------ 1 files changed, 9 insertions(+), 12 deletions(-)
fs/cramfs/README +9 -12
@@ -1,3 +1,12 @@ +Mount options +------------- + +Currently, there is only one mount option available for cramfs: + +swapendian: + causes the filesystem's metadata to be converted from + non-host-endianness to host-endianness. + Notes on Filesystem Layout --------------------------
@@ -108,18 +117,6 @@ kernels, not even necessarily kernels of the same architecture if PAGE_CACHE_SIZE is subject to change between kernel versions (currently possible with arm and ia64). -The remaining options try to make cramfs more sharable. - -One part of that is addressing endianness. The two options here are -`always use little-endian' (like ext2fs) or `writer chooses -endianness; kernel adapts at runtime'. Little-endian wins because of -code simplicity and little CPU overhead even on big-endian machines. - -The cost of swabbing is changing the code to use the le32_to_cpu -etc. macros as used by ext2fs. We don't need to swab the compressed -data, only the superblock, inodes and block pointers. - - The other part of making cramfs more sharable is choosing a block size. The options are: