From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/6] Xen DOM0 runtime support
Date: Thu, 22 Oct 2015 23:28:58 -0700 [thread overview]
Message-ID: <20151022232858.65498d27@xeon-e3> (raw)
In-Reply-To: <7433431.i8vU4GXoZ3@xps13>
On Wed, 21 Oct 2015 16:40:08 +0200
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> 2015-09-30 10:30, Stephen Hemminger:
> > On Wed, 30 Sep 2015 10:14:09 +0200
> > David Marchand <david.marchand@6wind.com> wrote:
> > > On Tue, Sep 29, 2015 at 2:44 AM, Stephen Hemminger <
> > > stephen@networkplumber.org> wrote:
> > > > It should be possible to build a single application or library
> > > > that will work both in Xen and non-Xen environment. Any special
> > > > case handling should be done at runtime.
> > >
> > > This patchset looks good, but can you go a step further and completely
> > > remove the RTE_LIBRTE_XEN_DOM0 build option ?
> > > This requires some more work (igb_uio, app/test), but I think this is worth
> > > it all the more so as you are looking into it at the moment.
> >
> > I was thinking that for people on embedded systems having
> > the build option (which stubs out support) was a good thing.
>
> No we must remove the config options.
> It is not in a hot path so there is no reason to disable this support.
> Please respin.
I looked into this, But Xen dom0 is a driver as well, and DPDK as is
makes all the drivers optional. Also, we don't use Xen dom0 directly
(only the net-front driver), and therefore do not have the infrastructure
to test that driver.
prev parent reply other threads:[~2015-10-23 6:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 0:44 [PATCH 0/6] Xen DOM0 runtime support Stephen Hemminger
2015-09-29 0:44 ` [PATCH 1/6] xen: allow determining DOM0 at runtime Stephen Hemminger
2015-10-21 14:41 ` Thomas Monjalon
2015-09-29 0:44 ` [PATCH 2/6] ethdev: add common function for reserving DMA regions Stephen Hemminger
2015-09-29 0:44 ` [PATCH 3/6] e1000: use rte_eth_dma_zone_reserve Stephen Hemminger
2015-09-29 0:44 ` [PATCH 4/6] ixgbe: " Stephen Hemminger
2015-09-29 0:44 ` [PATCH 5/6] i40e: " Stephen Hemminger
2015-09-29 0:44 ` [PATCH 6/6] fm10k: " Stephen Hemminger
2015-10-04 18:44 ` David Marchand
2015-10-21 14:37 ` Thomas Monjalon
2015-09-29 20:11 ` [PATCH 0/6] Xen DOM0 runtime support Liu, Jijiang
2015-09-30 8:14 ` David Marchand
2015-09-30 17:30 ` Stephen Hemminger
2015-10-21 14:40 ` Thomas Monjalon
2015-10-23 6:28 ` Stephen Hemminger [this message]
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=20151022232858.65498d27@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.