Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753830AbbGATC7 (ORCPT ); Wed, 1 Jul 2015 15:02:59 -0400 Received: from mail-ie0-f180.google.com ([209.85.223.180]:33337 "EHLO mail-ie0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753071AbbGATCv (ORCPT ); Wed, 1 Jul 2015 15:02:51 -0400 MIME-Version: 1.0 In-Reply-To: <20150701113150-mutt-send-email-mst@redhat.com> References: <20150701113150-mutt-send-email-mst@redhat.com> Date: Wed, 1 Jul 2015 12:02:50 -0700 X-Google-Sender-Auth: lq1iyALIKyofeHKL-ziZFfyYLZU Message-ID: Subject: Re: [PULL] virtio/vhost: cross endian support From: Linus Torvalds To: "Michael S. Tsirkin" Cc: KVM list , virtualization , Network Development , Linux Kernel Mailing List , Cornelia Huck , gkurz@linux.vnet.ibm.com, kraxel@redhat.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 731 Lines: 18 On Wed, Jul 1, 2015 at 2:31 AM, Michael S. Tsirkin wrote: > virtio/vhost: cross endian support Ugh. Does this really have to be dynamic? Can't virtio do the sane thing, and just use a _fixed_ endianness? Doing a unconditional byte swap is faster and simpler than the crazy conditionals. That's true regardless of endianness, but gets to be even more so if the fixed endianness is little-endian, since BE is not-so-slowly fading from the world. Linus -- 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/