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 15C31A0096 for ; Fri, 12 Apr 2019 09:12:27 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2019F559A; Fri, 12 Apr 2019 09:12:25 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by dpdk.org (Postfix) with ESMTP id DEFB32B95 for ; Fri, 12 Apr 2019 09:12:22 +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 x3C7A6Td009951; Fri, 12 Apr 2019 00:12:22 -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=dFvQvjq9216VQRtSNK2GcGb2kIq328Iqrp9rC6f9j/0=; b=Pc029eN4YCR/mcPKyBSKdIgGkrYGvAqePD3ET1jr7M7J87wayDjbBj5YRRC9bbD+N4uL fQIibxJFzIDhp/P+ciYkcMl6WwuNMgLJPn9O8grdneFqt6vcdWEuw/1oKhgSl3rOPSaZ wQ8slATc6hjL5ii+CitoxE0SQSNnAlvx5bN8Of7lHLZWceFTMMqtVaRjJtu6t8MhKozD x0Vchdk00ik08Jd3XxaYEPhHTLr9RaUAwstrltdZ90G8UAg5c0BXhBmYdoOY8DebMgoT HE2nzkoN/15F6Lwq25aaxVNuhEzGdV1tOWtzac09/X48fTvFq0oQQBp9Dqs26JCPMxWg 8w== Received: from sc-exch01.marvell.com ([199.233.58.181]) by mx0a-0016f401.pphosted.com with ESMTP id 2rtnqcg2vw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 12 Apr 2019 00:12:22 -0700 Received: from SC-EXCH04.marvell.com (10.93.176.84) by SC-EXCH01.marvell.com (10.93.176.81) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Fri, 12 Apr 2019 00:12:21 -0700 Received: from NAM04-SN1-obe.outbound.protection.outlook.com (104.47.44.52) by SC-EXCH04.marvell.com (10.93.176.84) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Fri, 12 Apr 2019 00:12:21 -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=dFvQvjq9216VQRtSNK2GcGb2kIq328Iqrp9rC6f9j/0=; b=cdu54q0D0kAcMCwU9r5Je2Q3CMkiEfIMSbja7aEKmqxsQRuaEYZvwq0arbYDBdJ/xRyB88KKkcn6HL/nu62hwQi1evHAlRiVTXCwiye314w5vFLjrkpmhUPl5dJU67LOhoMlHJw6aRu+uEbtmYIUzNzzoTmurthhAmnbuVu6erc= Received: from BYAPR18MB2424.namprd18.prod.outlook.com (20.179.91.149) by BYAPR18MB2536.namprd18.prod.outlook.com (20.179.93.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.18; Fri, 12 Apr 2019 07:12:18 +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.1771.019; Fri, 12 Apr 2019 07:12:18 +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+iXjS7cN1vMqY3n5YAgAB8OIA= Date: Fri, 12 Apr 2019 07:12:18 +0000 Message-ID: References: <20190406142737.20091-1-jerinj@marvell.com> <20190410161400.9361-1-jerinj@marvell.com> <20190410161400.9361-2-jerinj@marvell.com> <7046361.HPUSkOkSIl@xps> In-Reply-To: <7046361.HPUSkOkSIl@xps> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [122.182.194.144] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: d183ff77-16be-43d9-2a8a-08d6bf1632eb x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:BYAPR18MB2536; x-ms-traffictypediagnostic: BYAPR18MB2536: x-microsoft-antispam-prvs: x-forefront-prvs: 0005B05917 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(39860400002)(366004)(376002)(346002)(396003)(199004)(189003)(13464003)(6436002)(4326008)(256004)(3846002)(102836004)(14454004)(71190400001)(55016002)(71200400001)(2906002)(66066001)(99286004)(229853002)(7736002)(53546011)(186003)(6506007)(6116002)(53936002)(6636002)(25786009)(110136005)(54906003)(305945005)(97736004)(33656002)(7696005)(6246003)(86362001)(26005)(8936002)(5660300002)(74316002)(68736007)(476003)(8676002)(11346002)(81166006)(81156014)(106356001)(486006)(105586002)(478600001)(76176011)(93886005)(52536014)(316002)(446003)(9686003); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR18MB2536; H:BYAPR18MB2424.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: ASYuR5yU2ajkDlg+4pcYkFTgriOUvzRpLyFS4EHMuNquQI5XKRYU356pX73GSRghQFPhaCuLmN5eRGVfgMIirZmzOWg/f1Jn4K/DXfB5Ud72YH7uOKuCj4cDawG0Vf9ul/qS02TwgEkfdheylqoB2RM1GSNuM4I4BM6DWAPjzy9Gm3eJMlOmHc/nC+i5XO70ay7cp+6l95YC9ciHu61azDyPzHlXjnt2fUCrOdW3dmvrkwPEjzx25yWrUqlP1zOrvzRa63WnuJj8IgSvNQyy7IOaP3zZwhGC1lJ8gCEUYxVF/U74AqcywMlP7jxoMURcawzain13bJ+P185w2YuHjLKYh4Ka61NPZTaonjdXzmhTIwYH3561Z8hofeIwFc7ZbHsyZgg3TuQRzQ3ReUQte0zLw8TlhPOa37uvvXnPEMg= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: d183ff77-16be-43d9-2a8a-08d6bf1632eb X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2019 07:12:18.2120 (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: BYAPR18MB2536 X-OriginatorOrg: marvell.com X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-12_05:, , 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: <20190412071218.P22qyfubWBMiEWlD6fC-hTdDCNzWiK4x953KSQqr-dA@z> > -----Original Message----- > From: Thomas Monjalon > Sent: Friday, April 12, 2019 5:07 AM > To: Pavan Nikhilesh Bhagavatula ; Jerin Jacob > Kollanukkaran > Cc: 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 > 10/04/2019 18:13, jerinjacobk@gmail.com: > > From: Pavan Nikhilesh > > > > Currently, RTE_* flags are set based on the implementer ID but there > > might be some micro arch specific differences from the same vendor eg. > > CACHE_LINESIZE. Add support to set micro arch specific flags. >=20 > I don't like how flags are set in config/arm/meson.build. > It is a real mess to find which flag applies to which machine. > Adding the flags_*_extra in the machine_args_* is adding more mess. >=20 > [...] > > flags_common_default =3D [ > > # Accelarate rte_memcpy. Be sure to run unit test > (memcpy_perf_autotest) > > # to determine the best threshold in code. Refer to notes in source > > file @@ -52,12 +33,10 @@ flags_generic =3D [ > > ['RTE_USE_C11_MEM_MODEL', true], > > ['RTE_CACHE_LINE_SIZE', 128]] > > flags_cavium =3D [ > > - ['RTE_MACHINE', '"thunderx"'], > > ['RTE_CACHE_LINE_SIZE', 128], > > ['RTE_MAX_NUMA_NODES', 2], > > ['RTE_MAX_LCORE', 96], > > - ['RTE_MAX_VFIO_GROUPS', 128], > > - ['RTE_USE_C11_MEM_MODEL', false]] > > + ['RTE_MAX_VFIO_GROUPS', 128]] > > flags_dpaa =3D [ > > ['RTE_MACHINE', '"dpaa"'], > > ['RTE_USE_C11_MEM_MODEL', true], > > @@ -71,6 +50,27 @@ flags_dpaa2 =3D [ > > ['RTE_MAX_NUMA_NODES', 1], > > ['RTE_MAX_LCORE', 16], > > ['RTE_LIBRTE_DPAA2_USE_PHYS_IOVA', false]] > > +flags_default_extra =3D [] > > +flags_thunderx_extra =3D [ > > + ['RTE_MACHINE', '"thunderx"'], > > + ['RTE_USE_C11_MEM_MODEL', false]] > > + > > +machine_args_generic =3D [ > > + ['default', ['-march=3Darmv8-a+crc+crypto']], > > + ['native', ['-march=3Dnative']], > > + ['0xd03', ['-mcpu=3Dcortex-a53']], > > + ['0xd04', ['-mcpu=3Dcortex-a35']], > > + ['0xd07', ['-mcpu=3Dcortex-a57']], > > + ['0xd08', ['-mcpu=3Dcortex-a72']], > > + ['0xd09', ['-mcpu=3Dcortex-a73']], > > + ['0xd0a', ['-mcpu=3Dcortex-a75']]] > > + > > +machine_args_cavium =3D [ > > + ['default', ['-march=3Darmv8-a+crc+crypto','-mcpu=3Dthunderx']], > > + ['native', ['-march=3Dnative']], > > + ['0xa1', ['-mcpu=3Dthunderxt88'], flags_thunderx_extra], > > + ['0xa2', ['-mcpu=3Dthunderxt81'], flags_thunderx_extra], > > + ['0xa3', ['-mcpu=3Dthunderxt83'], flags_thunderx_extra]] >=20 > I think we should have a simpler model. > We need only to know the machine name and get all the related machine > config. > In native compilation, machine name is guessed from implementor id and pn > (from config/arm/armv8_machine.py). We can directly output the machine > name from this script and leave the naming logic in this script. > In the cross-compilation config files (config/arm/*), we can just specify= the > machine name. > Then every machine config (machine_args and dpdk_conf) would be > specified in some arrays based on the machine name. > Of course, we can keep some common default values. Thomas, This patch was around last three months. It reached upto v8. I think, in that last minute for RC2, We cannot take major rework on this a= s it needs to tested for Other arm64 platform too. It was pulled out from RC1 because other pcap iss= ue from meson. Now its not fair to say to rework the meson stuff now. I suggest to take other rework in next release. >=20 > Thoughts? >=20