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 75897A00C3; Wed, 7 Dec 2022 12:00:53 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5F25540F17; Wed, 7 Dec 2022 12:00:53 +0100 (CET) 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 B9CF140156 for ; Wed, 7 Dec 2022 12:00:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1670410852; 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=ayERPsZ8nB75ihXkWQhMqBXhqB9yZKebYonth8KxwOI=; b=MgHHSYCHLlMKjGX4kSK4NLzT/mGmY8koTa6KsoJVDV5c2WAZMOF2k+3gOpmvD2jA1gCjFU x3rNXfkjtLmOM5iClhShcVQactXRgnOSIjAB7WNn50N/88/s4F83Pd6EVmLPixlvtz1TTY Jje5vN8SLg60eXzCeJI38kEKMdam/U8= Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-661-XN0MqUyPMnWGzUk5f4ajSw-1; Wed, 07 Dec 2022 06:00:51 -0500 X-MC-Unique: XN0MqUyPMnWGzUk5f4ajSw-1 Received: by mail-wr1-f70.google.com with SMTP id w11-20020adfbacb000000b002418a90da01so4078092wrg.16 for ; Wed, 07 Dec 2022 03:00:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:references:to:from:subject:cc:message-id:date :content-transfer-encoding:mime-version:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=ayERPsZ8nB75ihXkWQhMqBXhqB9yZKebYonth8KxwOI=; b=aELCADwLnrlsLIKWwNy1SJFX6MXRS8J512GPLPa/LpRWPPlw1WB1Is2w04eKG8JyUj 6Ngkl7h58v0rRkn6i+0Cb2yPxbtG0ym0Ji8tjd4uZ+Rzc0EEY8OlkMF84ZqG7KWYkfBX qdCNqlIZZqKzjcyI4kTqX3kJKeSX9m53zCWnWqRUrdE973cmw9DQ4/gGvdDZ9HW4MWNP uoMEHbg2DAQOdNKKWno6jgGQAdj73zM/eGqepZiJEU/NzIcn6K8lTn0dSwpygmMgrfBH dCYxbp021bcEqt77hs1QGpDCQajMp/fJCQ+7GZ0kWf81emscURU6h701rdnhbiq9iz9E rR6A== X-Gm-Message-State: ANoB5plgErmmYGMTU3s5q5eYxvQIV7zANg0reJp5zX6TdXicN9iSyi+v yGItgDfZlQc25gvYrSnDY3+8LkfdLirSg0+QDGRf86sJe5MP1douHuFpAg9nno43NYnFKEVQ+88 H8Ow= X-Received: by 2002:a5d:674e:0:b0:242:40c4:a805 with SMTP id l14-20020a5d674e000000b0024240c4a805mr14947829wrw.372.1670410849979; Wed, 07 Dec 2022 03:00:49 -0800 (PST) X-Google-Smtp-Source: AA0mqf5S6BcxVhcGp8WZBgPW3zaYCVbaA9yEHU1bIR2itpe1hctS3GU2aE/g7We7tCj+2CB7njxBQQ== X-Received: by 2002:a5d:674e:0:b0:242:40c4:a805 with SMTP id l14-20020a5d674e000000b0024240c4a805mr14947811wrw.372.1670410849725; Wed, 07 Dec 2022 03:00:49 -0800 (PST) Received: from localhost (2a01cb000f483e0055ae3800781b5cbc.ipv6.abo.wanadoo.fr. [2a01:cb00:f48:3e00:55ae:3800:781b:5cbc]) by smtp.gmail.com with ESMTPSA id t64-20020a1c4643000000b003cfa622a18asm1292204wma.3.2022.12.07.03.00.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 07 Dec 2022 03:00:49 -0800 (PST) Mime-Version: 1.0 Date: Wed, 07 Dec 2022 12:00:48 +0100 Message-Id: Cc: =?utf-8?q?Morten_Br=C3=B8rup?= Subject: Re: [PATCH v3 2/4] eal: allow applications to report their cpu cycles usage From: "Robin Jarry" To: =?utf-8?q?Mattias_R=C3=B6nnblom?= , X-Mailer: aerc/0.13.0-121-g11bda62d2dff-dirty References: <20221123102612.1688865-1-rjarry@redhat.com> <20221129153329.181652-1-rjarry@redhat.com> <20221129153329.181652-3-rjarry@redhat.com> <27c377b2-d8ef-8d71-c7a3-04d03458b272@lysator.liu.se> In-Reply-To: <27c377b2-d8ef-8d71-c7a3-04d03458b272@lysator.liu.se> X-Mimecast-Spam-Score: 1 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hi Mattias, Mattias R=C3=B6nnblom, Nov 29, 2022 at 17:10: > > + * @param [out] busy_cycles > > + * The number of busy CPU cycles since the application start. > > Wouldn't it be more appropriate to describe it as "TSC cycles", instead= =20 > of "CPU cycles"? Or technically "The amount of busy time since=20 > application start, in TSC cycles". > > Reporting actual CPU core cycles spent is not possible, in the general ca= se. Well, technically, these "cycles" could mean anything. You could report the number of microseconds, Joules, whatever. The important information is the ratio compared to the total number of "cycles". Perhaps Morten's suggestion (units) would be more precise, but I fear it would also be more confusing. I don't mind adding the specific TSC cycles nomenclature if there is a consensus. Cheers