Received: by 2002:a05:7412:8d10:b0:f3:1519:9f41 with SMTP id bj16csp5638254rdb; Wed, 13 Dec 2023 15:03:10 -0800 (PST) X-Google-Smtp-Source: AGHT+IEuukTSwq1TISJMUHtf6g9IaEhAiyGDRSVrqY5d73+pSdlBdTT8dQ1GzpcsBFDjH5UpKyti X-Received: by 2002:a17:907:d9e:b0:a1c:ccbf:dc98 with SMTP id go30-20020a1709070d9e00b00a1cccbfdc98mr5182360ejc.42.1702508590585; Wed, 13 Dec 2023 15:03:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702508590; cv=none; d=google.com; s=arc-20160816; b=u1u7ILT6oqc2XgQKZMA1Tl05JnkZ6kAW9/0XNxdSpko5kbX8uBJI1fCLALO6wdra+w BxnB7e7mIYjLgWZg9XZw2DdKIiEzs65mTyp9NFOjjLwR2ewbzTk3oF3TvVgHu6U395lP +gVhEvbjTnFp3kZZHpPDRtFakP1mfeHfpOg08FGFfvnG/X84aTmI9sdmE4eQLPzHURx4 3uUQuDPhWLqzvkM84md4zpKT87spQfzCk3tSubcay02Gd+k+wPd8SVs6xGLFnath14N1 JR2ggZbisUvNY/aHi1hvD2sOJDvyDqCGuLHfM0niiNWKOkczKbsjqWZw4ekiVikvIDeq Jh8g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:list-unsubscribe:list-subscribe:list-id:precedence :user-agent:content-transfer-encoding:references:in-reply-to:date:cc :to:from:subject:message-id:dkim-signature; bh=fYl5wQQq326IZgGiR+nK2duHby21YVK9vwiAkhi0t1g=; fh=w/m6O0HQij49eCeB35lnsIBV++r2912d+s3zDqsOYiY=; b=X+rsniQcye7N3NHyk6u5Zf+lYmjYwtzz1PDEIcDV27QKUdSlLx5Q4bGyfmOudR7rlL 2qgll/4v9cthoVE2cjQA/vza5Zu6y+hxO9cA9YjhC5K/eQ8mwKkYcpdT9L1RiVO1DwZs Saz8/KowrFkH0QQ4u5KWLVvCWjk6FmO9M1fKhivUgusqw0A5WtOrsCjKcfq7+8USyfg4 f/TlI28HlJkfuwOU12iMecLbUwb84AUDuitgs+vXCkbGJs5YCMzdobTf1dl59qN4A+i7 CYAVYsKJXz+cSnLytRPWcJUjGsSmP/vCyrIa5B59RYN+EOGQZLN6P69c/xld+G8TQPhe SgWQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=bZr20q86; spf=pass (google.com: domain of linux-crypto+bounces-821-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-crypto+bounces-821-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [147.75.80.249]) by mx.google.com with ESMTPS id o15-20020a17090637cf00b00a1df3f9b2c2si5729189ejc.445.2023.12.13.15.03.10 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Dec 2023 15:03:10 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto+bounces-821-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=bZr20q86; spf=pass (google.com: domain of linux-crypto+bounces-821-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-crypto+bounces-821-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id 4B8E61F218C0 for ; Wed, 13 Dec 2023 23:03:10 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 4BD958185F; Wed, 13 Dec 2023 23:03:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="bZr20q86" X-Original-To: linux-crypto@vger.kernel.org Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.8]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5E95D99; Wed, 13 Dec 2023 15:03:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1702508584; x=1734044584; h=message-id:subject:from:to:cc:date:in-reply-to: references:content-transfer-encoding:mime-version; bh=cozZxSkGzieURXERb/Sy+rCeOm0TXgG9x/5Y7sy6lZE=; b=bZr20q86e/vhN4hjORXbSnglGLEtIi2CYT0P/OQTTwip50KWkJr1IHSN ZSSd+8qTpiKv+OJ93X7KmoinhmSeR0V4nMq63yYue9RWeflnS7oUsmk9E timfGgYLit/CRWbXKKtvr5HiQZB6t946QWGIu5zBaYr7vxYVDbGg+NJw+ HiWjnDPjDHV+XBgiPhtguWURU0T6Q9Qeh/8odOreAgaXp89ZQOTQcoVNJ 1ySsxDIun1srSoNxGxnMjOU5J0BZMrcq6+gJ5GGzeGwhf9r7qY9muFk9S 23BqAAd3mkmSdxIcg6ZKuVP+WZNQd/qJCx3o2t7pA0kf37GqBz/+JMY3r w==; X-IronPort-AV: E=McAfee;i="6600,9927,10923"; a="8434935" X-IronPort-AV: E=Sophos;i="6.04,274,1695711600"; d="scan'208";a="8434935" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmvoesa102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Dec 2023 15:03:03 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10923"; a="750297780" X-IronPort-AV: E=Sophos;i="6.04,274,1695711600"; d="scan'208";a="750297780" Received: from wanghuan-mobl1.amr.corp.intel.com (HELO [10.212.178.119]) ([10.212.178.119]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Dec 2023 15:03:02 -0800 Message-ID: <3287f6c9d5fb68a8ef915c0e7af8f3a6a262cd89.camel@linux.intel.com> Subject: Re: [PATCH] crypto: tcrypt - add script tcrypt_speed_compare.py From: Tim Chen To: Wang Jinchao Cc: Herbert Xu , "David S. Miller" , Steffen Klassert , Daniel Jordan , linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, stone.xulei@xfusion.com Date: Wed, 13 Dec 2023 15:03:02 -0800 In-Reply-To: References: <202312101758+0800-wangjinchao@xfusion.com> <118d0b232f7daffc56db814f90dba7bad266c5ab.camel@linux.intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4 (3.44.4-2.fc36) Precedence: bulk X-Mailing-List: linux-crypto@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 On Wed, 2023-12-13 at 11:01 +0800, Wang Jinchao wrote: > On Tue, Dec 12, 2023 at 01:56:56PM -0800, Tim Chen wrote: > > On Sun, 2023-12-10 at 18:19 +0800, WangJinchao wrote: > > > Create a script for comparing tcrypt speed test logs. > > > The script will systematically analyze differences item > > > by item and provide a summary (average). > > > This tool is useful for evaluating the stability of > > > cryptographic module algorithms and assisting with > > > performance optimization. > >=20 > > I have found that for such comparison, the stability is > > dependent on whether we allow the frequency to > > float or we pin the frequency. So in the past when > > I use tcrypt, sometimes I have > > to pin the frequency of CPU for stable results. > >=20 > > One suggestion I have is for for you to also dump the > > frequency governor and P-state info so we know > > for the runs being compared, whether they are running > > with the same CPU frequency. > >=20 > > Tim=20 > >=20 > Thank you for the feedback. This information is valuable for stability te= sting > and performance optimization. >=20 > However, I am uncertain about how to dump P-state information, or I belie= ve that > the script is unable to do so. The reasons are as follows: >=20 > 1. The primary purpose of this script is to compare tcrypt logs, and it i= s > executed after the completion of the tcrypt tests. Consequently, it canno= t > dump P-state information during tcrypt's runtime. >=20 > 2. In virtualized environments, there is no available information in the > `/sys/devices/system/cpu/cpufreq` directory pertaining to P-state details= . >=20 > Am I correct in my understanding? > I am considering documenting your suggestion in the script's comments. > What are your thoughts? > >=20 I think that will be fine.=20 Thanks. Tim