From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6AAE1A04DD; Thu, 19 Nov 2020 09:39:51 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 61E4D4C90; Thu, 19 Nov 2020 09:39:50 +0100 (CET) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 75805F90 for ; Thu, 19 Nov 2020 09:39:46 +0100 (CET) IronPort-SDR: My2tTUiGj6id/t2teqk9powmbBLqt0UvRbTzdfF/koPe3Ke1WE70zQHewcNDB/3+6vC4cDPDCD fcXYVg2w7+rQ== X-IronPort-AV: E=McAfee;i="6000,8403,9809"; a="171352803" X-IronPort-AV: E=Sophos;i="5.77,490,1596524400"; d="scan'208";a="171352803" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Nov 2020 00:39:45 -0800 IronPort-SDR: XZPXMa5oMIwa/lIxWrnmz5tjGam4Z0f0BfZ8PubRAz8J9EPHUFLQwYDu8LsvWobhIzB1MKFjoM yEPph6cefqOw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,490,1596524400"; d="scan'208";a="476727792" Received: from fmsmsx603.amr.corp.intel.com ([10.18.126.83]) by orsmga004.jf.intel.com with ESMTP; 19 Nov 2020 00:39:45 -0800 Received: from shsmsx606.ccr.corp.intel.com (10.109.6.216) by fmsmsx603.amr.corp.intel.com (10.18.126.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 19 Nov 2020 00:39:44 -0800 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX606.ccr.corp.intel.com (10.109.6.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 19 Nov 2020 16:39:42 +0800 Received: from shsmsx601.ccr.corp.intel.com ([10.109.6.141]) by SHSMSX601.ccr.corp.intel.com ([10.109.6.141]) with mapi id 15.01.1713.004; Thu, 19 Nov 2020 16:39:42 +0800 From: "Tu, Lijuan" To: "Zhao, HaiyangX" , "dts@dpdk.org" CC: "Zhao, HaiyangX" Thread-Topic: [dts][PATCH V1 0/2] framework: fix meson compile failed when set rx mode Thread-Index: AQHWvXEHnKU8GoAUXUiLiiGTW22e+6nPJBJQ Date: Thu, 19 Nov 2020 08:39:42 +0000 Message-ID: References: <20201118060114.14553-1-haiyangx.zhao@intel.com> In-Reply-To: <20201118060114.14553-1-haiyangx.zhao@intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-version: 11.5.1.3 dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] [PATCH V1 0/2] framework: fix meson compile failed when set rx mode X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Sender: "dts" > The rx modes are supported dynamically since DPDK 20.11, and by modifying > the DPDK configuration to use the rx mode is only supported by makefile > compiling , so need add a jugement. > And only add rx mode eal parameter for meson compile type. >=20 >=20 > Haiyang Zhao (2): > framework/project_dpdk: fix meson compile failed when set rx mode > framework/dut: optmize code when setting eal param for rx mode >=20 > framework/dut.py | 4 +++- > framework/project_dpdk.py | 43 ++++++++++++++++++++++----------------- > 2 files changed, 27 insertions(+), 20 deletions(-) >=20 Applied