All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Drebes <lists-receive@programmierforen.de>
To: linux-fsdevel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PATCH 0/2] cramfs: update README file
Date: Thu, 15 Nov 2007 21:37:27 +0100	[thread overview]
Message-ID: <200711152137.28105.lists-receive@programmierforen.de> (raw)
In-Reply-To: <200711152129.25686.lists-receive@programmierforen.de>

This patch updates the readme file according to the
new mount option "swapendian".

Signed-off-by: Andi Drebes <andi@programmierforen.de>
---
 fs/cramfs/README |   21 +++++++++------------
 1 files changed, 9 insertions(+), 12 deletions(-)

diff --git a/fs/cramfs/README b/fs/cramfs/README
index 445d1c2..acbbdc4 100644
--- a/fs/cramfs/README
+++ b/fs/cramfs/README
@@ -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:
 

  parent reply	other threads:[~2007-11-15 20:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 20:29 [PATCH 0/2] cramfs: support for other endianness Andi Drebes
2007-11-15 20:35 ` [PATCH 0/2] cramfs: Add mount option "swapendian" Andi Drebes
2007-11-15 20:45   ` Linus Torvalds
2007-11-15 20:46     ` Linus Torvalds
2007-11-15 20:51       ` Christoph Hellwig
2007-11-15 20:49     ` Christoph Hellwig
2007-11-15 20:57       ` Linus Torvalds
2007-11-15 21:15     ` Andi Drebes
2007-11-15 21:37       ` Linus Torvalds
2007-11-15 22:48         ` Phillip Lougher
2007-11-16 10:28           ` Andi Drebes
2007-11-16 15:44             ` Linus Torvalds
2007-11-15 21:03   ` Jörn Engel
2007-11-15 20:37 ` Andi Drebes [this message]
2007-11-15 20:43 ` [PATCH 0/2] cramfs: support for other endianness Andi Drebes

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=200711152137.28105.lists-receive@programmierforen.de \
    --to=lists-receive@programmierforen.de \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.