From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 43399C43331 for ; Thu, 26 Mar 2020 02:59:19 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id C09A920719 for ; Thu, 26 Mar 2020 02:59:18 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C09A920719 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 04C721C02B; Thu, 26 Mar 2020 03:59:18 +0100 (CET) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 6BEB71C029 for ; Thu, 26 Mar 2020 03:59:16 +0100 (CET) IronPort-SDR: UxSYsqTxxmbJVGSQ8AxJxzoiGfuNwB/egtLXomTpN3MSn50jIGStfiFfQhwn4j3ldoRsS3Qe7l jR55SnxUX/rw== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Mar 2020 19:59:15 -0700 IronPort-SDR: 9rFonKOLAVSvFpqDLy+pWdltF0xK704COqzO2ll6HPChXpnNZhNAWNcblM2mnd5jOOebW/eDs8 ymaFM4IKvbfA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.72,306,1580803200"; d="scan'208";a="448477281" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga006.fm.intel.com with ESMTP; 25 Mar 2020 19:59:15 -0700 Received: from fmsmsx155.amr.corp.intel.com (10.18.116.71) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 25 Mar 2020 19:59:14 -0700 Received: from FMSMSX109.amr.corp.intel.com ([169.254.15.183]) by FMSMSX155.amr.corp.intel.com ([169.254.5.71]) with mapi id 14.03.0439.000; Wed, 25 Mar 2020 19:59:14 -0700 From: "Chautru, Nicolas" To: Akhil Goyal , "dev@dpdk.org" Thread-Topic: [PATCH v3 10/14] test-bbdev: vectors update Thread-Index: AQHV8lZ0t0lwmIuZvkmtE6kZn1UHeKhZ67eAgABkLoA= Date: Thu, 26 Mar 2020 02:59:14 +0000 Message-ID: <1183128033837D43A851F70F33ED5C576EFD272D@FMSMSX109.amr.corp.intel.com> References: <1582778348-113547-15-git-send-email-nicolas.chautru@intel.com> <1583348102-13253-1-git-send-email-nicolas.chautru@intel.com> <1583348102-13253-11-git-send-email-nicolas.chautru@intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-originating-ip: [10.1.200.106] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v3 10/14] test-bbdev: vectors update 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" From: Akhil Goyal =20 >> From: Nic Chautru >>=20 >> Modification to vectors parameters used for unit test for coverage and=20 >> performance test of bbdev drivers across all devices. >> Reducing list for focused coverage when required. >>=20 >> Signed-off-by: Nic Chautru > >Not able to get the reason for removing these vectors. >Please explain more in the commit log. > I have added some reason in the commit message, mainly historical and focus= ing on configuration that make more sense for functional coverage. Modification to vectors parameters used for unit test for coverage and performance test of bbdev drivers across all devices. Updating and reducing list for focused coverage on relevant code blocks for 4G and 5G. Less focus on 4G TB mode as there is some question how to best support this with mbuf limitations and if effect are not used. Removing scenarios with negative LLR assumptions which are not used with any PMDs and historical only.