DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xie, Huawei" <huawei.xie@intel.com>
To: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>,
	"Thomas Monjalon" <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] building LIBRTE_PMD_XENVIRT in 32bit triggers some	errors
Date: Thu, 10 Dec 2015 04:45:06 +0000	[thread overview]
Message-ID: <C37D651A908B024F974696C65296B57B4BB88AEF@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CAJSM8J2k-okd6VCMQd_V+aE39Pvs9zyhDusdcTocybDbjj9K4w@mail.gmail.com>

On 12/10/2015 6:49 AM, Martinx - ジェームズ wrote:
> On 9 December 2015 at 18:05, Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
>> 2015-12-09 15:54, Martinx - ジェームズ:
>>>  Sorry to insist on this subject but, the time for releasing DPDK 2.2
>>> is near and DPDK build with Xen 32-bit is broken.
>>>
>>>  If DPDK doesn't fix this, there will be no way to enable XenVirt
>>> support for next Ubuntu LTS 16.04, which is a shame...
>>>
>>>  I'm planning to use DPDK on Xen domUs (PVM, HVM, XenServer and on
>>> Amazon EC2) powered exclusively by a supported version of Ubuntu but,
>>> it is broken now...
>>>
>>>  So, please, can someone take a look into this?    :-P
>>>
>>>  Thanks in advance!
>> Sorry, this area has no maintainer:
>>         http://dpdk.org/browse/dpdk/tree/MAINTAINERS#n169
>>
>> In such case, it may be logic to remove the dead code.
>> If someone wants to make it alive, he's welcome!
> Hi Thomas,
>
>  Listen, if DPDK on Xen has no maintainer, where can I find the
> current state of DPDK on Xen?
>
>  I mean, I'm planning to use DPDK with Xen on the following environments:
>
>  * Amazon EC2 - HVM Enhanced Networking - *priority*
>  * XenServer
>  * Open Source Xen on Debian / Ubuntu (both PVM / HVM)
>
>  But, if Xen support on DPDK has no maintainer, how to you guys are
> running DPDK on top of Xen (like for example, within Amazon EC2)?
>
>  If I google for "DPDK Xen", I can find lots of good information but,
> I can't find recommended setup / drivers...
>
>  Do you have any recommendation?
Thiago:
This xen PMD is based on grant table mechanism and virtio interface.
Worth to note is it needs customized backend, which now resides in
examples/vhost_xen.
Another approach is netfront based PMD, which has kernel netback backend
in place, but i guess it couldn't achieve best performance as we need
map each grant page in backend. Stephen submitted the patch for netfront
PMD http://dpdk.org/dev/patchwork/patch/3330/. Thomas, do you know its
status?
Anyway i will try to create the XEN environment, and check the issues.

>
>  Thank you!
>
> Best,
> Thiago
>


  reply	other threads:[~2015-12-10  4:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 14:05 Christian Ehrhardt
2015-12-04 23:56 ` Martinx - ジェームズ
2015-12-09 17:54   ` Martinx - ジェームズ
2015-12-09 20:05     ` Thomas Monjalon
2015-12-09 22:48       ` Martinx - ジェームズ
2015-12-10  4:45         ` Xie, Huawei [this message]
2015-12-10  8:51           ` Thomas Monjalon
2015-12-21 18:03           ` Martinx - ジェームズ
2015-12-22  2:51             ` Xie, Huawei

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=C37D651A908B024F974696C65296B57B4BB88AEF@SHSMSX103.ccr.corp.intel.com \
    --to=huawei.xie@intel.com \
    --cc=dev@dpdk.org \
    --cc=thiagocmartinsc@gmail.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).