DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Ilya Maximets <i.maximets@samsung.com>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>,
	Yuanhan Liu <yliu@fridaylinux.org>,
	Heetae Ahn <heetae82.ahn@samsung.com>
Subject: Re: [dpdk-dev] technical board meeting, 2017-06-07
Date: Wed, 7 Jun 2017 12:18:48 +0100	[thread overview]
Message-ID: <20170607111848.GA47000@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <9126fc60-6c20-4c2d-2f90-4f2388920416@samsung.com>

On Wed, Jun 07, 2017 at 12:45:43PM +0300, Ilya Maximets wrote:
> Hello everyone,
> 
> I wanted to remind the question about 'external dependencies'
> and off-by-default policy for the new features.
> 
> Currently, I'm interested in adding libnuma as a general dependency
> for LIBRTE_EAL as suggested by Sergio Gonzalez Monroy in discussion
> of balanced allocation of hugepages.
> 
> Most recent patchset located here:
> http://dpdk.org/ml/archives/dev/2017-June/067337.html
> 
> It fails to build on the test servers right now because of not
> installed libnuma-devel package.
> 
> Previous discussion was in this thread:
> http://dpdk.org/ml/archives/dev/2017-April/063442.html
> 
> Maybe you can add this topic to agenda?
> 
> Unfortunately I'll not be able to join the meeting, but I'd
> like to hear your opinions and read the discussion log and
> meeting-minutes later.
>

Thanks for bringing this up again.

Rather than taking the incremental approach to bolting on new features
to our build system, please see the RFC I've just submitted to take the
"nuclear option" and try and wholesale replace our config and build with
better alternatives, and give us a more standard build approach.

Please take the patch for a test-drive and let me know what you think.

Regards,
/Bruce

      reply	other threads:[~2017-06-07 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 16:40 Stephen Hemminger
     [not found] ` <CGME20170607094545eucas1p2d77d683df268c13561a5f6fe42526778@eucas1p2.samsung.com>
2017-06-07  9:45   ` Ilya Maximets
2017-06-07 11:18     ` Bruce Richardson [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=20170607111848.GA47000@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=heetae82.ahn@samsung.com \
    --cc=i.maximets@samsung.com \
    --cc=sergio.gonzalez.monroy@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=yliu@fridaylinux.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 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).