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 92C214240F; Wed, 18 Jan 2023 17:46:40 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 71F9440223; Wed, 18 Jan 2023 17:46:40 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 8B079400D6 for ; Wed, 18 Jan 2023 17:46:39 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1674060399; 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=IIEJtiGpz8MO4l6dodXVd6mlF7wfi5qDwntAJagzfiY=; b=Mm5M3L0g1ld/SDvytoR9d23qLVu+GG6zfdQgtSaCHG04/4XgBKSVSa2acBBjxCUrZQpYEg 8aXhmNHAEHMus4PBHNijKczmicE6wjIqOIfDuOEhv8TpO9Cqtdh/O/BlH022jS+H7hODDY JPxorPQcWtNlW4PnRIEXAsGirwg+pwU= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-248-5S5kiN98MayYuxhLRydJYA-1; Wed, 18 Jan 2023 11:46:37 -0500 X-MC-Unique: 5S5kiN98MayYuxhLRydJYA-1 Received: by mail-wr1-f69.google.com with SMTP id m12-20020adfa3cc000000b002b881cb0cb4so7009826wrb.3 for ; Wed, 18 Jan 2023 08:46:37 -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=IIEJtiGpz8MO4l6dodXVd6mlF7wfi5qDwntAJagzfiY=; b=AqBD6/5vliGs4WoX4CkyeHonXSlO6ohe2m68zyh3anPihQwmuFCz6xXCtfgBXfex+W 0DTgSJx03paIe6RS+tbLY8tEB9Ok2sTk3R4ggZliFBLdUUrvDlDkKqyPElHntqWfaO2g ApwdSHpmoVVAicInznjgG7UbM6VLjTjNU15H725JOsfvSQjNVEgjUr4sX2UOanCstONd hkN+/nc1aa+Z6os+spZZ3eja4afJgD2zt1CZV/VXTcsILJSLLZzA7F2ozEY8vQNQXkmX HSCE0RaIrJBGk0jO0VDt81I9Bokdbtj01B/YecI/8SU/3TeasFXSYhK46q2D2iGGmU8c 7cpw== X-Gm-Message-State: AFqh2koa+x1KlcGPM7dij0t0Vit4JwycpEPjDN1b74xdjVyogAxmDfJC 3ux1OvLoWeOqRguqYMdI3pSY8rd8Us1YLEPsda9AcSZ6fENd8tX4CLBj65ma8AnUa/W22f/EjOt WOvU= X-Received: by 2002:a05:600c:3ba9:b0:3da:b40f:7a55 with SMTP id n41-20020a05600c3ba900b003dab40f7a55mr14285640wms.6.1674060396842; Wed, 18 Jan 2023 08:46:36 -0800 (PST) X-Google-Smtp-Source: AMrXdXuYAyEe0E1EMP13HM6/mnhYcl6SaHOmzagUFqbNFIFfS8TjFX7FGu39JJ96WsAdHFJ9UIxiiw== X-Received: by 2002:a05:600c:3ba9:b0:3da:b40f:7a55 with SMTP id n41-20020a05600c3ba900b003dab40f7a55mr14285631wms.6.1674060396652; Wed, 18 Jan 2023 08:46:36 -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 p18-20020a05600c359200b003db040f0d5esm2551858wmq.33.2023.01.18.08.46.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Jan 2023 08:46:36 -0800 (PST) Mime-Version: 1.0 Date: Wed, 18 Jan 2023 17:46:35 +0100 Message-Id: Cc: "Tyler Retzlaff" , "Kevin Laatz" , =?utf-8?q?Morten_Br=C3=B8rup?= Subject: Re: [PATCH v5 2/4] eal: allow applications to report their cpu usage From: "Robin Jarry" To: "Konstantin Ananyev" , "dev@dpdk.org" X-Mailer: aerc/0.14.0-31-g01280214150a-dirty References: <20221123102612.1688865-1-rjarry@redhat.com> <20221216102109.64142-1-rjarry@redhat.com> <20221216102109.64142-3-rjarry@redhat.com> In-Reply-To: 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 Konstantin Ananyev, Jan 04, 2023 at 11:53: > Probably we can even print warning or so if some-one tries to overwrite > it once again. I'm not sure that is necessary. If an application wants to reset the callback to NULL at any point in time, I don't see why DPDK should tell them it is a bad thing.