From: Stephen Hemminger <stephen@networkplumber.org>
To: "Liu, Jijiang" <jijiang.liu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Stephen Hemminger <shemming@brocade.com>
Subject: Re: [dpdk-dev] [PATCH 1/4] xen: allow choosing dom0 support at runtime
Date: Sun, 15 Feb 2015 09:27:47 -0500 [thread overview]
Message-ID: <20150215092747.2f6a4822@uryu.home.lan> (raw)
In-Reply-To: <1ED644BD7E0A5F4091CF203DAFB8E4CC01DDC7CB@SHSMSX101.ccr.corp.intel.com>
On Sun, 15 Feb 2015 04:07:21 +0000
"Liu, Jijiang" <jijiang.liu@intel.com> wrote:
> Hi Stephen,
>
> What do you mean ' allow choosing dom0 support at runtime'?
> If you mean user can choose DPDK to run Xen Dom0 or not on DOM0 by a runtime flag, I don't think your change can achieve this goal.
>
> Thanks
> Jijiang Liu
With the existing DPDK model if application is built with DOM0 support
it will not work (it crashes) if the application is run in a non DOM0
environment (with real huge pages). And vice-versa if application is built
without DOM0 support and it will crash if run in Xen Paravirt mode.
This patch allows the library to be built in such a way that only one
version needs to be shipped which is important for distro's like RHEL
who want to ship a shared library. And also important for users like
Brocade/Vyatta who build one binary that needs to work on bare Linux
and in Xen PV mode.
next prev parent reply other threads:[~2015-02-15 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 4:07 Liu, Jijiang
2015-02-15 14:27 ` Stephen Hemminger [this message]
2015-02-26 6:53 ` Liu, Jijiang
2015-02-26 7:05 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2015-02-14 18:06 Stephen Hemminger
2015-02-14 19:25 ` Neil Horman
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=20150215092747.2f6a4822@uryu.home.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jijiang.liu@intel.com \
--cc=shemming@brocade.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).