From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Pavel Fedin <sonic.amiga@gmail.com>
Cc: maximilian attems <max@baikonur.stro.at>,
Matthew Wilcox <matthew@wil.cx>,
linux-fsdevel@vger.kernel.org
Subject: Re: Corrupted ASFS patch.
Date: Thu, 12 Feb 2009 09:42:42 +0000 [thread overview]
Message-ID: <4993EF12.8040209@lougher.demon.co.uk> (raw)
In-Reply-To: <85766219.20090212112447@gmail.com>
Pavel Fedin wrote:
> Third, this is the question fot Matthew, about annotating endianess
> in on-disk structures. What if the filesystem is bi-endian? Original
> SFS (http://sourceforge.net/projects/smartfilesystem) is bi-endian. I
> still don't know how much of support for little-endian version is implemented
> in Linux version.
>
This issue has come up before (over Squashfs which used to be
'bi-endian'). The general consensus is that all Linux filesystems
should be one endianness only, as it potentially simplifies code and
makes it more efficient (i.e. the swap code can be conditionally
compiled).
As SFS is not a native Linux filesystem you could argue that the
bi-endian layout is a legacy feature over which you have no control.
However, unless there are a lot of little-endian SFS filesystems
out there, supporting them is likely to give you more pain than
it's worth, and it will present an additional barrier to mainlining.
Phillip
next prev parent reply other threads:[~2009-02-12 9:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 13:18 Corrupted ASFS patch Pavel Fedin
2009-02-09 13:31 ` maximilian attems
2009-02-12 8:24 ` Re[2]: " Pavel Fedin
2009-02-12 9:42 ` Phillip Lougher [this message]
2009-02-12 10:52 ` Pavel Fedin
2009-02-12 16:38 ` Phillip Lougher
2009-02-13 6:53 ` [PATCH 1/9] Amiga SmartFileSystem, revision 2 Pavel Fedin
2009-02-13 6:54 ` [PATCH 2/9] " Pavel Fedin
2009-02-13 6:55 ` [PATCH 3/9] " Pavel Fedin
2009-02-13 6:55 ` [PATCH 4/9] " Pavel Fedin
2009-02-13 6:56 ` [PATCH 5/9] " Pavel Fedin
2009-02-13 6:56 ` [PATCH 6/9] " Pavel Fedin
2009-02-13 6:56 ` [PATCH 7/9] " Pavel Fedin
2009-02-13 6:57 ` [PATCH 8/9] " Pavel Fedin
2009-02-13 6:57 ` [PATCH 9/9] " Pavel Fedin
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=4993EF12.8040209@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=max@baikonur.stro.at \
--cc=sonic.amiga@gmail.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;
as well as URLs for NNTP newsgroup(s).