From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 29DC1459AA; Mon, 16 Sep 2024 09:17:07 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F00294025F; Mon, 16 Sep 2024 09:17:06 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 2787440041 for ; Mon, 16 Sep 2024 09:17:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1726471025; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WXPk7BaDBge/vFxiE0IUBHtjSzMRaEKUtaGPAIdoS5s=; b=gcmJbjOYYIfiC8D4HNM+Ri7glLhOV51mF/ddaGR658FnWVTLp5YMkMQvS8nora3X64Ce0V yXQqSljOy7FXSEKXCrOZADnuxw9Gl9gbDxno3GYuZQ9CZnvfmBSV1DW03b4BhHlM8oftcE 4zvmT6iZHwpL3MF7CpI94vYX8Fmt404= Received: from mail-lj1-f199.google.com (mail-lj1-f199.google.com [209.85.208.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-93-otM-N2FOPDS69Ep_bqR5Tg-1; Mon, 16 Sep 2024 03:17:04 -0400 X-MC-Unique: otM-N2FOPDS69Ep_bqR5Tg-1 Received: by mail-lj1-f199.google.com with SMTP id 38308e7fff4ca-2f75ea32971so19053641fa.1 for ; Mon, 16 Sep 2024 00:17:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726471023; x=1727075823; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=WXPk7BaDBge/vFxiE0IUBHtjSzMRaEKUtaGPAIdoS5s=; b=n+XvgVFZMVpe47wVhkjt3+45kMrVYXNdWNbCgxrkxF12blnG6pU6lOYvy9T/N3uRbK gtRl+jB+dZP3GpxMOZGQCrlCY4+4HaB/yPTgPtGMKe6aK4kDeU3Nv2VWm9S/KX1oUZu0 JcI5X5NZA+SVwVes4wPwaku2dMojb9FDrRQIU5uG9mPXLV0TigrXM/A7pZT1N3YL5Nah LV7nq2T+rKg/b6dkdN7t6xALdGHjNf2eGlrLt2VfBKdpVr/gSymcoE5ymN4Uei55WJOl zUDcjf8/4kIj1oj0lmT3h4AAJmYtHP7zfKhsmF9pTAEa/FyWFzQDalb9hSTM0L12U6Ij Dbhw== X-Gm-Message-State: AOJu0Yz4WgWbw85wLiN2VXwJP1y5kR3z+C7OiMIOattQnwM6TtRYQ7px 08HqTmXTEBM45+sEq4SmhsPx9bDOZhB41kLibAAZdN3tADtO7xQlYAaFitLVUHJameuPiBHDZE7 qeQOtluIUBMV/u7pBWRG6A+547RrE7X39VCdTXdcTL56SEVg5rE3GSRTpB7BU/Br0LsvbS1ok2v I1goaBasb92hY8pAc= X-Received: by 2002:a2e:611a:0:b0:2f7:6129:5804 with SMTP id 38308e7fff4ca-2f7919fc705mr38701141fa.15.1726471022790; Mon, 16 Sep 2024 00:17:02 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFS9phpmwNJ5PUTop7jf8bDHhS71zavk7MRNjb6Nkb+ragtoCCC5hjRew9LDFvNhZ8xd6CKRi8i6oTMMDFhbh4= X-Received: by 2002:a2e:611a:0:b0:2f7:6129:5804 with SMTP id 38308e7fff4ca-2f7919fc705mr38700971fa.15.1726471022249; Mon, 16 Sep 2024 00:17:02 -0700 (PDT) MIME-Version: 1.0 References: <20240916042631.186816-1-probb@iol.unh.edu> In-Reply-To: <20240916042631.186816-1-probb@iol.unh.edu> From: David Marchand Date: Mon, 16 Sep 2024 09:16:50 +0200 Message-ID: Subject: Re: [PATCH] tests/TestSuite_crypto_perf_cryptodev_perf.py Improving lscpu parsing To: Patrick Robb Cc: dts@dpdk.org, Thomas Monjalon , Aaron Conole X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 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 On Mon, Sep 16, 2024 at 6:27=E2=80=AFAM Patrick Robb wr= ote: > > This testsuite fails to parse lscpu output on some systems because > it expects that there be no leading whitespace, which is not > true on all systems. The leading whitespace is a generic issue, not really related to "some" sys= tems. The issue is that keys of interest for the rest of the code ('Core(s) per socket', 'Socket(s)', 'CPU(s)') may have leading whitespace on some systems. Could you detail which systems have such issue? In any case, this fix makes sense to me and it seems limited and safe enough to merge the patch in the "legacy" repository for dts. > > Signed-off-by: Patrick Robb Reviewed-by: David Marchand --=20 David Marchand