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 2EF26A04A3; Tue, 16 Jun 2020 04:40:39 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BDDEB2B94; Tue, 16 Jun 2020 04:40:38 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id C032325B3 for ; Tue, 16 Jun 2020 04:40:37 +0200 (CEST) IronPort-SDR: L36xVLiVLEGzAvTDViJkOHwpNpOb45gbY4R9dNkRHbeJorza3h1oGYEpIhBvYVQCm3n53hRozh LAKR6H/HqJUw== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Jun 2020 19:40:36 -0700 IronPort-SDR: 3PrpJFRwXXC8UpQsycklqqljLV+VfZFh5brqY37NWJQQzkrgyHLnFl80SjAp8FiA9vVW0bDGBN FN6a8OK06Ncw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,517,1583222400"; d="scan'208";a="476263000" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga005.fm.intel.com with ESMTP; 15 Jun 2020 19:40:36 -0700 Received: from shsmsx603.ccr.corp.intel.com (10.109.6.143) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.439.0; Mon, 15 Jun 2020 19:40:36 -0700 Received: from shsmsx605.ccr.corp.intel.com (10.109.6.215) by SHSMSX603.ccr.corp.intel.com (10.109.6.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 16 Jun 2020 10:40:33 +0800 Received: from shsmsx605.ccr.corp.intel.com ([10.109.6.215]) by SHSMSX605.ccr.corp.intel.com ([10.109.6.215]) with mapi id 15.01.1713.004; Tue, 16 Jun 2020 10:40:33 +0800 From: "Mo, YufengX" To: "dts@dpdk.org" , "Chen, Zhaoyan" Thread-Topic: [dts][PATCH V3 0/1] tests/dcf_lifecycle: upload test plan and automation script Thread-Index: AQHWQ4asQVS3Izz2ZESTNT61wymG5qjah+FQ Date: Tue, 16 Jun 2020 02:40:33 +0000 Message-ID: <1a390729a75a4f47b63de96a055bc627@intel.com> References: <20200616023450.16143-1-yufengx.mo@intel.com> In-Reply-To: <20200616023450.16143-1-yufengx.mo@intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: 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 V3 0/1] tests/dcf_lifecycle: upload test plan and automation script 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" Tested by Mo, YufengX > -----Original Message----- > From: Mo, YufengX > Sent: Tuesday, June 16, 2020 10:35 AM > To: dts@dpdk.org; Chen, Zhaoyan > Cc: Mo, YufengX > Subject: [dts][PATCH V3 0/1] tests/dcf_lifecycle: upload test plan and au= tomation script >=20 > The DCF is a device configuration function (DCF - driver) bound to > one of the device's VFs which can act as a sole controlling entity > to exercise advance functionality (such as switch, ACL) for rest of > the VNFs (virtual network functions) under a DPDK based NFV deployment. >=20 > The DCF can act as a special VF talking to the kernel PF over the same > virtchannel mailbox to configure the underlying device (port) for the VFs= . >=20 > The test suite covers the lifecycle of DCF context in Kernel PF, such as > launch, and exit, switch rules handling, resetting, and exception exit. >=20 > v3: > - *. remove TC07-TC10 test cases. >=20 > v2: > - *. update script for dpdk 20.08 rc0 on new CVL nic. >=20 > yufengmx (1): > tests/dcf_lifecycle: upload automation script >=20 > tests/TestSuite_dcf_lifecycle.py | 1175 ++++++++++++++++++++++++++++++ > 1 file changed, 1175 insertions(+) > create mode 100644 tests/TestSuite_dcf_lifecycle.py >=20 > -- > 2.21.0