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 9B5AF41C25; Mon, 6 Feb 2023 21:39:55 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 38E3640A7D; Mon, 6 Feb 2023 21:39:55 +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 ACC7640156 for ; Mon, 6 Feb 2023 21:39:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675715993; 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=mMiIXNCtyzu1dF99QjBZsxUHLr2fjlfyiMor2B5cGZU=; b=UPLATGB4zxTJd/c3SPOrqOosk5MRLYYLuUFDZR3M3jl3ohLXrYxZmhL9phE1qfLcsfFEMu xnKDjUewqHMOEmhjAn9woyrU4IJtdKfZnMR9u+43JP4hJK+IrSm+LkT4DGlnJN6OhshvGU QKsmgYDi62X2Kl0B4K3gNLcVkKMrjmU= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-107-TeUOkV1KMvOKQkkLhyMmWQ-1; Mon, 06 Feb 2023 15:39:52 -0500 X-MC-Unique: TeUOkV1KMvOKQkkLhyMmWQ-1 Received: by mail-wm1-f70.google.com with SMTP id k17-20020a05600c1c9100b003dd41ad974bso7110851wms.3 for ; Mon, 06 Feb 2023 12:39:51 -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=mMiIXNCtyzu1dF99QjBZsxUHLr2fjlfyiMor2B5cGZU=; b=JRSn4xhg/KuSu2aqvgD4HVqlhjVCGFsZuqoaHLWCOWPkGxIqEQQjSA8ozNn3gXH1NG fU/MIGZIn+9Xmc07Kr5JiG4FpccOQauObG3r/F1N/0O8c9kvMf3mRV0AvL7gf+DmcfL5 5Z0L1k+qfetHqt0b3xuEr3VBfLrOEeKgEB5wgcmUKIHo42WWK0tvx04jY7Qqz1tVzKNU R2dnYoeLLNdqPY1NsDvUWQvqqBBZ1SWZLbKzwhll6oobaSGIUIORUdaca5rSLZsnyRIn jdFkfqM7wgRmx+58lo6mdp/2FZk1/Jg/F7hqm+B7HIdbLXf+hJEeeAy7C4Qx3imjm0zd DO+A== X-Gm-Message-State: AO0yUKUZMGh3/8lK0MVH0KnowoFDqZx59YHEYNILZla/sNOmJwT5eFSy chbv8rPmw9RMuz1vDT6lqCPd1qqX8D6/P891RXkq7aEc8JcWIgYwteGRRaoyju8d2BvLXia+ndg Cc94= X-Received: by 2002:adf:e592:0:b0:2bf:eb0e:cccc with SMTP id l18-20020adfe592000000b002bfeb0eccccmr165570wrm.43.1675715990964; Mon, 06 Feb 2023 12:39:50 -0800 (PST) X-Google-Smtp-Source: AK7set/l+8AWlqMZavI4ckGC9PDSSpdmTcdLL/TfGlqjBNSBvOAgbXxt0UaEjZQ8472IbhTWs2WdVg== X-Received: by 2002:adf:e592:0:b0:2bf:eb0e:cccc with SMTP id l18-20020adfe592000000b002bfeb0eccccmr165558wrm.43.1675715990750; Mon, 06 Feb 2023 12:39:50 -0800 (PST) Received: from localhost (2a01cb000f483e00b4815b62aee6aa5b.ipv6.abo.wanadoo.fr. [2a01:cb00:f48:3e00:b481:5b62:aee6:aa5b]) by smtp.gmail.com with ESMTPSA id o15-20020adfa10f000000b002bddaea7a0bsm9762239wro.57.2023.02.06.12.39.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Feb 2023 12:39:50 -0800 (PST) Mime-Version: 1.0 Date: Mon, 06 Feb 2023 21:39:49 +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-64-gf10d00f8407e References: <20221123102612.1688865-1-rjarry@redhat.com> <20221216102109.64142-1-rjarry@redhat.com> <20221216102109.64142-3-rjarry@redhat.com> <9456959e61754f9394321e33a01746db@huawei.com> In-Reply-To: <9456959e61754f9394321e33a01746db@huawei.com> 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, Feb 06, 2023 at 21:34: > Yes, app knows what resources it wants to free. > But it has no way to know *when* it is safe to free them. > Just a bit more explanation: > App invokes your function which resets global value of CB. > How would it know that after return from this function none > other thread still not executing this CB right now? > And how determine when this thread will finish with executing CB function= ? > That's why it might be easier simply not allow to reset it at all.... Ok I see. But what should we do to prevent this? Simply ignore the request and log a warning?