From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 986DD2BA1 for ; Fri, 9 Jun 2017 20:06:06 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga105.fm.intel.com with ESMTP; 09 Jun 2017 11:06:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,319,1493708400"; d="scan'208";a="1180488208" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga002.fm.intel.com with ESMTP; 09 Jun 2017 11:06:05 -0700 Received: from fmsmsx152.amr.corp.intel.com (10.18.125.5) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 9 Jun 2017 11:06:05 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.162]) by FMSMSX152.amr.corp.intel.com ([169.254.6.102]) with mapi id 14.03.0319.002; Fri, 9 Jun 2017 11:06:04 -0700 From: "Wiles, Keith" To: "Richardson, Bruce" CC: Christian Ehrhardt , Stephen Hemminger , dev Thread-Topic: [dpdk-dev] [RFC PATCH] replace DPDK config and build system Thread-Index: AQHS33+Qm2nQKlKxc0a/5f5gWdnRAaIagUWAgACgBoCAAH0nAIAAG/mAgAD68oCAAJcaAA== Date: Fri, 9 Jun 2017 18:06:04 +0000 Message-ID: <946E12D3-50BD-49DF-A73F-F29896C7DDDD@intel.com> References: <20170607104743.275149-1-bruce.richardson@intel.com> <20170607162617.00d009ff@xeon-e3> <20170608085901.GC58216@bricha3-MOBL3.ger.corp.intel.com> <20170608092658.6a4bfc5c@xeon-e3> <20170609090515.GB59768@bricha3-MOBL3.ger.corp.intel.com> In-Reply-To: <20170609090515.GB59768@bricha3-MOBL3.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.143.237] Content-Type: text/plain; charset="us-ascii" Content-ID: <40411D108FC48540A5CC573DB1B5BA89@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [RFC PATCH] replace DPDK config and build system X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jun 2017 18:06:07 -0000 > On Jun 9, 2017, at 4:05 AM, Bruce Richardson = wrote: >=20 > On Thu, Jun 08, 2017 at 12:07:05PM -0600, Christian Ehrhardt wrote: >> On Thu, Jun 8, 2017 at 10:26 AM, Stephen Hemminger < >> stephen@networkplumber.org> wrote: >>=20 >>> On a side note, it would be good to use the GCC extensions that allow >>> building different versions of the same routine into one binary. >>>=20 >>=20 >> And we are back to the discussion we had two years ago about how to deli= ver >> generic yet also optimized binaries in one shot. >> But if the new build system can enable us to do so I'm all in for that. >>=20 >> Thanks for bringing this up in that context Stephen - might be just the >> right time to look at it again. >>=20 > Yep, we can do that. First though, we need to decide what our minimum > supported compiler baseline is going to be. > Also, if the replace the build system, do we want to do a complete > on-shot replacement, or do we want to keep the older one around in > parallel for a while e.g. to support older OS's and compilers. I think it would be a good idea to keep the old version for now. I would suggest adding the new build system to a sandbox repo until we thin= k we have parity then merge into main. Keep the old system in place to allo= w for other systems until we believe we really have covered all of the base= s. What would your baseline be ? I would suggest pick a few distros like Linux Ubuntu, Fedora, Red Hat just = a guess at the ones we need to support first. Think we have to support IA and ARM at the same time for the few distros we= start with first or at least pick the most used one for ARM first.=20 >=20 > /Bruce Regards, Keith