From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Fedin Subject: Re[2]: Corrupted ASFS patch. Date: Thu, 12 Feb 2009 13:52:16 +0300 Message-ID: <927229715.20090212135216@gmail.com> References: <187c6cc60902090518vf8589a7nb9ee0ad30e618a03@mail.gmail.com> <20090209133120.GF24188@baikonur.stro.at> <85766219.20090212112447@gmail.com> <4993EF12.8040209@lougher.demon.co.uk> Reply-To: Pavel Fedin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org To: Phillip Lougher Return-path: Received: from mail-bw0-f167.google.com ([209.85.218.167]:57815 "EHLO mail-bw0-f167.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754589AbZBLKwS (ORCPT ); Thu, 12 Feb 2009 05:52:18 -0500 Received: by bwz11 with SMTP id 11so419444bwz.13 for ; Thu, 12 Feb 2009 02:52:16 -0800 (PST) In-Reply-To: <4993EF12.8040209@lougher.demon.co.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hello Phillip, Thursday, February 12, 2009, 12:42:42 PM, you wrote: > 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. I've asked Michal Schulz at AROS IRC channel, he told me that little-endian version was introduced as experimental and it did not gave any significant speedup (just 1%). This ended its life - support for little-endian SFS exists only in theory, it is not adviced for production use, not supported by formatting and installation tools, etc. So far the issue is closed. SFS is bigendian. End of story. Do i understand right that i just need to replace all 'uXX' with 'beXX' in on-disk structures definition ? -- Best regards, Pavel mailto:sonic.amiga@gmail.com