Date: Fri, 24 Apr 2015 16:39:09 +0200
From: Michele Curti <michele.curti@gmail.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
        Havoc Pennington <hp@pobox.com>,
        Austin S Hemmelgarn <ahferroin7@gmail.com>,
        Andy Lutomirski <luto@amacapital.net>,
        "Eric W. Biederman" <ebiederm@xmission.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Arnd Bergmann <arnd@arndb.de>,
        One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
        Tom Gundersen <teg@jklm.no>, Jiri Kosina <jkosina@suse.cz>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Daniel Mack <daniel@zonque.org>,
        David Herrmann <dh.herrmann@gmail.com>,
        Djalal Harouni <tixxdz@opendz.org>
Subject: Re: Issues with capability bits and meta-data in kdbus
Message-ID: <20150424143909.GA21054@dellaz>
References: <87oamhmbso.fsf_-_@x220.int.ebiederm.org>
 <CA+55aFwqhbN=1Tm71AFHtXeOUut5gcLpqRmH=6R1H92grDsVrw@mail.gmail.com>
 <CALCETrX+z2xqvpG=UHm5JoA_dSupug9fwphkKR3YYy8FdXivFA@mail.gmail.com>
 <CA+55aFzL22XjeyPuapc+mYe1fEco8ZY7doJzSF9vPLwGU9taXA@mail.gmail.com>
 <553788A9.6090006@gmail.com>
 <CAEntwhH1PAAu9_hHoXv=YuAA81sk=8BALjO-DStPJM6BgMk5Ng@mail.gmail.com>
 <20150422143515.GA23155@dellaz>
 <CAEntwhF8xhT1YiZWCESML=+qfQ3n2HDgrf_W1JboNGf869-JHA@mail.gmail.com>
 <CA+55aFwvz7ssxGQNZPrLO2nP60TuaWXu=yx0LzN82cQDCD1+pQ@mail.gmail.com>
 <20150424143212.GA27730@aepfle.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150424143212.GA27730@aepfle.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 912
Lines: 26

On Fri, Apr 24, 2015 at 04:32:12PM +0200, Olaf Hering wrote:
> On Wed, Apr 22, Linus Torvalds wrote:
> 
> > Conditional byte order is worse than silly - it's terminally stupid.
> 
> > In other words, think networking, which statically just decided to use
> > big-endian. Sure, that was the wrong choice in the end, but even
> 
> Why was that wrong? Any pointers to further details?
>

http://www.barrgroup.com/Embedded-Systems/How-To/Big-Endian-Little-Endian

"Serious run-time performance penalties occur when using TCP/IP on a little
endian processor."

The Intel x86 and x86-64 series of processors use the little-endian format

I think for this reason..

Michele
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/