From: Matthew Hall <mhall-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
To: "Gonzalez Monroy,
Sergio"
<sergio.gonzalez.monroy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH RFC] Update/Improve build system
Date: Thu, 30 Oct 2014 13:50:00 -0700 [thread overview]
Message-ID: <20141030205000.GA9956@mhcomputing.net> (raw)
In-Reply-To: <91383E96CE459D47BCE92EFBF5CE73B004E97FFB-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Thu, Oct 30, 2014 at 09:18:23AM +0000, Gonzalez Monroy, Sergio wrote:
> I would say that D) is a good balance, although not being the simplest.
A, or D. Depending on things such as, "If you run the DPDK on Random Platform
X," where X could be something like Power CPUs or other weird stuff, will all
of the things needed for the Combined Lib 1) be compilable, 2) be able to load
w/o errors.
For example, I could see probe ctor functions from various PMD's blowing up on
unsupported hardware. Like how the rte_pmd_virtio had issues when I tried it
on my VM system.
If we think we can make sure no platform specific stuff breaks when it ends up
in Combined Lib A then A is probably the easiest for all.
Matthew.
next prev parent reply other threads:[~2014-10-30 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 9:18 [PATCH RFC] Update/Improve build system Gonzalez Monroy, Sergio
[not found] ` <91383E96CE459D47BCE92EFBF5CE73B004E97FFB-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-10-30 11:53 ` Gonzalez Monroy, Sergio
2014-10-30 20:50 ` Matthew Hall [this message]
[not found] ` <20141030205000.GA9956-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
2014-10-31 10:45 ` Gonzalez Monroy, Sergio
[not found] ` <91383E96CE459D47BCE92EFBF5CE73B004E9AAFB-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-10-31 22:33 ` Matthew Hall
2014-11-01 12:53 ` 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=20141030205000.GA9956@mhcomputing.net \
--to=mhall-hv3ognyu3jfzzajbqzqcxq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=sergio.gonzalez.monroy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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.