From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 7571D5A50 for ; Sun, 1 Nov 2015 12:22:09 +0100 (CET) Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id 8114C8CF57; Sun, 1 Nov 2015 11:22:08 +0000 (UTC) Received: from [10.36.7.143] (vpn1-7-143.ams2.redhat.com [10.36.7.143]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tA1BM6iR015397; Sun, 1 Nov 2015 06:22:06 -0500 To: Thomas Monjalon , "Michael S. Tsirkin" References: <1444907319-26348-1-git-send-email-marcel@redhat.com> <2413695.XHLO16SCPC@xps13> <5635D4C8.4030407@redhat.com> <1963243.g88CBzixeL@xps13> From: Marcel Apfelbaum Message-ID: <5635F5DB.1050605@redhat.com> Date: Sun, 1 Nov 2015 13:22:03 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <1963243.g88CBzixeL@xps13> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27 Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] vhost-user: enable virtio 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2015 11:22:09 -0000 On 11/01/2015 11:53 AM, Thomas Monjalon wrote: > 2015-11-01 11:00, Marcel Apfelbaum: >> On 10/30/2015 07:48 PM, Thomas Monjalon wrote: >>> 2015-10-18 10:04, Michael S. Tsirkin: >>>> This will require more work then as 1.0 is a different >>>> endian-ness from 0.9. It's up to you guys to decide >>>> whether correct BE support is now a requirement for all >>>> new dpdk code. Let us know. >> >>> I'm not sure to understand. >>> Yes DPDK must work on big endian platforms. >>> Does this patch prevent from using virtio 0.9 with big endian? >> >> No, if it worked until now, will continue to work. (And the other way around) >> >> However, if virtio 1.0 is supported by both QEMU and vhost-user, >> virtio 1.0 has different endianess requirements than prev virtio, > > OK so that's an acceptable workaround: big endian platforms must use > virtio 0.9. > > In order to have a big endian support of virtio 1.0, is it sufficient to > convert data? Is it something we want regarding performance? I think that converting the data should be enough, however Michael can give a more knowledgeable answer, we'll have to wait a few days for him as he is not available this week. Thanks, Marcel >