From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 3C4A3A00E6 for ; Sun, 14 Apr 2019 20:19:44 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 07E55569B; Sun, 14 Apr 2019 20:19:43 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by dpdk.org (Postfix) with ESMTP id 2BB30325F for ; Sun, 14 Apr 2019 20:19:41 +0200 (CEST) Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x3EI0BOr032232; Sun, 14 Apr 2019 11:19:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=pfpt0818; bh=bZjw5p6uo0eIzKATKr2UQ7T1FAK1CR9CEKlIVgHBOzM=; b=C0taR58sPfcw9hp1OXZCDhO6TyKj09f5ZeDubjyLGnO/OlnB2XMPI5qNnhCsJ7qQIFVG xDiwrUAhtNYBi/w93KW1u1kNYcqJ7ipamnGe9zZCKkVaa6DJGLZ/CJtzo7AsMG3XeQA0 YCCn60YMGmWMKrQJFRY/q4r3HKO3vIqfdM6iBw7+g58QBAu7oEr+hXsuUMr7pGxTvOVN Wz1IgNUkJnGKXNrg+9/f+yn4Es3wClsVfuwZ1lHGgGvGS+ja/vfUGKAs4SapnAgrIfkA abQ2tpjLAGlMhiD2o13ko0aO8oNNz3TVndqSEAyTVNs8l/jaFw66/ohp6y8BG5zS6htn 5g== Received: from sc-exch02.marvell.com ([199.233.58.182]) by mx0a-0016f401.pphosted.com with ESMTP id 2rud4nkydc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 14 Apr 2019 11:19:39 -0700 Received: from SC-EXCH04.marvell.com (10.93.176.84) by SC-EXCH02.marvell.com (10.93.176.82) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Sun, 14 Apr 2019 11:19:39 -0700 Received: from NAM04-CO1-obe.outbound.protection.outlook.com (104.47.45.55) by SC-EXCH04.marvell.com (10.93.176.84) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Sun, 14 Apr 2019 11:19:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.onmicrosoft.com; s=selector1-marvell-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bZjw5p6uo0eIzKATKr2UQ7T1FAK1CR9CEKlIVgHBOzM=; b=AFLuKs+lHuM+lte43U0PlUenwQGtm4v8PcoUmqWFMI2tW4yWFMT33yz/oZOboRKv+CfPNKq50gWotwYMnIMXP/aYX1dq7bnTmeKF5yk+nQiC1cCeyUMoooSi7MPWkHg0mq8VUsatF3ameEUH8/wt2kRkbbBK/FPLQtxJIfwctPY= Received: from BYAPR18MB2424.namprd18.prod.outlook.com (20.179.91.149) by BYAPR18MB2935.namprd18.prod.outlook.com (20.179.59.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.17; Sun, 14 Apr 2019 18:19:33 +0000 Received: from BYAPR18MB2424.namprd18.prod.outlook.com ([fe80::6dd3:c056:b23b:ab4e]) by BYAPR18MB2424.namprd18.prod.outlook.com ([fe80::6dd3:c056:b23b:ab4e%7]) with mapi id 15.20.1792.018; Sun, 14 Apr 2019 18:19:33 +0000 From: Jerin Jacob Kollanukkaran To: Thomas Monjalon , Pavan Nikhilesh Bhagavatula CC: "dev@dpdk.org" , "jerinjacobk@gmail.com" , "yskoh@mellanox.com" , "bruce.richardson@intel.com" Thread-Topic: [dpdk-dev] [PATCH v8 2/4] meson: add infra to support machine specific flags Thread-Index: AQHU77iSorMd3V4+3E+iXjS7cN1vMqY3n5YAgAB8OICAABzUgIABaIuQgADyTACAAS0ZAIAAM1gAgAAEarA= Date: Sun, 14 Apr 2019 18:19:33 +0000 Message-ID: References: <20190406142737.20091-1-jerinj@marvell.com> <3120421.JkTWNKALu9@xps> <1966190.OdWs8lNuHB@xps> In-Reply-To: <1966190.OdWs8lNuHB@xps> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [116.68.105.114] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 960c89ad-dffd-4bb1-21fd-08d6c105be9a x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:BYAPR18MB2935; x-ms-traffictypediagnostic: BYAPR18MB2935: x-microsoft-antispam-prvs: x-forefront-prvs: 00073DB75F x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39840400004)(346002)(396003)(136003)(376002)(13464003)(189003)(199004)(86362001)(97736004)(486006)(25786009)(11346002)(14444005)(4326008)(186003)(446003)(33656002)(105586002)(53936002)(3846002)(476003)(68736007)(26005)(256004)(6246003)(71190400001)(106356001)(71200400001)(8936002)(6506007)(53546011)(9686003)(102836004)(7696005)(7736002)(2906002)(52536014)(76176011)(6116002)(8676002)(81156014)(316002)(55236004)(14454004)(478600001)(66066001)(6436002)(74316002)(93886005)(99286004)(54906003)(110136005)(6636002)(55016002)(81166006)(5660300002)(229853002)(305945005); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR18MB2935; H:BYAPR18MB2424.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: marvell.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: wTWonMwmZMK+J5SIJoK8IgMORDYlsJiQn9/UXrVPgXzrjYM2Jib8SthQbAIZd4SP3uZ6CEyRCgjdQGssTkDk10YMCGozYz3k1B7cowxZEtYTzJ/qTAzExb3VHdOXi8uISs2UMPpmjetKea/L8ox4HuT0Z8UrSzbEqwIS6QbZ+b7zFSra6cl1nPHQpS4qvderg9qPjEv7RBu1RPwm3PmPlq9wmEXyuOjnvl/Hrxn+a5DclQIwZoyLd0vbVjNfmvzfUH8Bu+nMxj44o9D1UeYfHC+VJZXXpA+9Bvs2mrduupkTi1FzuqU2ZVp9FURShuPW/SzVJ2sjllzvQiZ0UjmVCXnTgZchli2w6vz3VEa7Yi1P5odDVQo58pUgSracqDA5vhd0nU7nmyoU4KIzemkfMrnx1Th1uZMDxv8h0UjZFMc= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 960c89ad-dffd-4bb1-21fd-08d6c105be9a X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Apr 2019 18:19:33.5122 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 70e1fb47-1155-421d-87fc-2e58f638b6e0 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR18MB2935 X-OriginatorOrg: marvell.com X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-14_06:, , signatures=0 Subject: Re: [dpdk-dev] [PATCH v8 2/4] meson: add infra to support machine specific flags 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190414181933.0X2-T5_KboP5BXekjLg4Jrrhus0HMPui8Ay7CWiGk_o@z> > -----Original Message----- > From: Thomas Monjalon > Sent: Sunday, April 14, 2019 11:14 PM > To: Pavan Nikhilesh Bhagavatula > Cc: Jerin Jacob Kollanukkaran ; dev@dpdk.org; > jerinjacobk@gmail.com; yskoh@mellanox.com; bruce.richardson@intel.com > Subject: Re: [dpdk-dev] [PATCH v8 2/4] meson: add infra to support machin= e > specific flags >=20 > 14/04/2019 16:40, Pavan Nikhilesh Bhagavatula: > > Hi Thomas, > > > > There is no guarantee of primary part number (machine names) uniqueness > between implementors. >=20 > I think we don't speak the same language :) By machine name, I mean what = we > set in RTE_MACHINE, like octeontx2. As you know, The system probes "implementor_id" and "implementor_pn" Values. There is nothing like machine name in meson and in order to keep=20 Synergy with native build, we need to just follow, "implementor_id" and "implementor_pn". Now, it is possible to have "implemetor_id" to "implementor_pn" to machine name lookup but Unlike, "make" based Build system, meson supports supporting a lot of machines(like RTE_MACHINE)= , with that structure. So converting to another intermediate called "machine = string" will have more overhead IMO. ['0xa1', ['-mcpu=3Dthunderxt88']], ['0xa2', ['-mcpu=3Dthunderxt81']], ['0xa3', ['-mcpu=3Dthunderxt83']]] ['0xd03', ['-mcpu=3Dcortex-a53']], ['0xd04', ['-mcpu=3Dcortex-a35']], ['0xd05', ['-mcpu=3Dcortex-a55']], ['0xd07', ['-mcpu=3Dcortex-a57']], ['0xd08', ['-mcpu=3Dcortex-a72']], ['0xd09', ['-mcpu=3Dcortex-a73']], ['0xd0a', ['-mcpu=3Dcortex-a75']], ['0xd0b', ['-mcpu=3Dcortex-a76']] impl_0x41 =3D ['Arm', flags_generic, machine_args_generic] impl_0x42 =3D ['Broadcom', flags_generic, machine_args_generic] impl_0x43 =3D ['Cavium', flags_cavium, machine_args_cavium] impl_0x44 =3D ['DEC', flags_generic, machine_args_generic] impl_0x49 =3D ['Infineon', flags_generic, machine_args_generic] impl_0x4d =3D ['Motorola', flags_generic, machine_args_generic] impl_0x4e =3D ['NVIDIA', flags_generic, machine_args_generic] impl_0x50 =3D ['AppliedMicro', flags_generic, machine_args_generic] impl_0x51 =3D ['Qualcomm', flags_generic, machine_args_generic] impl_0x53 =3D ['Samsung', flags_generic, machine_args_generic] impl_0x56 =3D ['Marvell', flags_generic, machine_args_generic] impl_0x69 =3D ['Intel', flags_generic, machine_args_generic] impl_dpaa =3D ['NXP DPAA', flags_dpaa, machine_args_generic] impl_dpaa2 =3D ['NXP DPAA2', flags_dpaa2, machine_args_generic] >=20 > > If we limit lookups to only machine names through primary part number w= e > would have a lot of repetitive defines. > > Also, moving the arrays into the python script is not feasible as > > meson needs to reparse the standard out from the python script >=20 > I will probably need to write a PoC. Yes. Please >=20 > > Currently, config is split into three parts : > > 1. Implementor specific defines. > > 2. Micro-arch specific compiler flags. > > 3. Micro-arch specific defines. >=20 > This is currently unreadable in my opinion. Bit subjective. If we want to keep all the fine grained control along with "native" /"cross" build, "distribution" build, cache line differences etc, makes it bit difficult. But if you think, it can be improved. Please share patch, We are happy to review and test in the platforms we have. > > I think from a configurability point of view the above three are really > important for fine grained control. >=20 > I agree fine grain is required. >=20 >=20 > > Thoughts? > > > > Regards, > > Pavan. > > > > >-----Original Message----- > > >From: Thomas Monjalon > > >Sent: Sunday, April 14, 2019 2:13 AM > > >To: Jerin Jacob Kollanukkaran > > >Cc: Pavan Nikhilesh Bhagavatula ; > > >dev@dpdk.org; jerinjacobk@gmail.com; yskoh@mellanox.com; > > >bruce.richardson@intel.com > > >Subject: Re: [dpdk-dev] [PATCH v8 2/4] meson: add infra to support > > >machine specific flags > > > > > >13/04/2019 08:24, Jerin Jacob Kollanukkaran: > > >> > I was not confortable with this patch without being able to say wh= y. > > >> > Yesterday I spent more time to understand and see what may be > improved. > > >> > I agree it is late, so it won't block this patch for 19.05. > > >> > Do you agree this file can be improved? > > >> > > >> Moving to the all to static config file is an option but we lose > > >> the flexibility of runtime detecting the options and few of them > > >> are probing at runtime based on gcc versions and mcpu combination et= c. > > > > > >I think there is a misunderstanding. > > >I'm suggesting to symplify arrays by indexing only by machine name. > > >It should not change the behaviour. > > > > > >> I am not expert in meson area and not sure meson/python has better > > >> data strcture for this other than list/array combo. If Bruce has > > >> any feedback on this, then we will try to prototype it. > > >> > > >> > Please would you like to look at reworking during next cycle? > > >> > Thanks > > > > > > > > > > >=20 >=20 >=20 >=20