DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel@redhat.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost-user: enable virtio 1.0
Date: Sun, 1 Nov 2015 13:22:03 +0200	[thread overview]
Message-ID: <5635F5DB.1050605@redhat.com> (raw)
In-Reply-To: <1963243.g88CBzixeL@xps13>

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

>

  reply	other threads:[~2015-11-01 11:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 11:08 Marcel Apfelbaum
2015-10-15 13:18 ` Michael S. Tsirkin
2015-10-16  2:24   ` Yuanhan Liu
2015-10-16  6:20     ` Michael S. Tsirkin
2015-10-16  7:43       ` Andriy Berestovskyy
2015-10-16  7:50         ` Yuanhan Liu
2015-10-16  7:56         ` Michael S. Tsirkin
2015-10-16 13:52   ` Bruce Richardson
2015-10-18  7:04     ` Michael S. Tsirkin
2015-10-30 17:48       ` Thomas Monjalon
2015-11-01  9:00         ` Marcel Apfelbaum
2015-11-01  9:53           ` Thomas Monjalon
2015-11-01 11:22             ` Marcel Apfelbaum [this message]
2015-11-09 19:55         ` Michael S. Tsirkin
2015-11-02 22:13   ` Thomas Monjalon
2015-11-03  3:45     ` Xu, Qian Q
2015-11-03  3:49       ` Xu, Qian Q
2015-11-03  8:03         ` Marcel Apfelbaum
2015-11-03  8:16           ` Xie, Huawei
2015-11-03  8:26             ` Thomas Monjalon
2015-11-03  8:30               ` Marcel Apfelbaum
2015-11-03  8:31             ` Marcel Apfelbaum
2015-10-16  6:39 ` Yuanhan Liu

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=5635F5DB.1050605@redhat.com \
    --to=marcel@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mst@redhat.com \
    --cc=thomas.monjalon@6wind.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).