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 7201245A9D; Wed, 2 Oct 2024 17:57:32 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3E8AC4027C; Wed, 2 Oct 2024 17:57:32 +0200 (CEST) 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 3323B40268 for ; Wed, 2 Oct 2024 17:57:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1727884649; 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; bh=7jAuWqybW5go9a2AKWQihCKG3K5MB+E8qsUZIuTuNXs=; b=gzw7eCLhXO+C1qpaKlzEiJ7WUW6epoyrXobA+g87l0kZw4nug0wcoYmbeWeI5jx80i/2Wu Sg8EBth5L7ucaQKXcSgJvRUexCP0ejH5KIDUv7bs5U2hIgeU5pDf8CwYQeqh19iEO7mc6p mfS9e+FTGbZPF4UE1CYCnhJXxmQoHew= Received: from mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-570-I2mdYWQDO52kcoCscD3O1Q-1; Wed, 02 Oct 2024 11:57:26 -0400 X-MC-Unique: I2mdYWQDO52kcoCscD3O1Q-1 Received: from mx-prod-int-04.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-04.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id A775D1953955; Wed, 2 Oct 2024 15:57:25 +0000 (UTC) Received: from dmarchan.redhat.com (unknown [10.45.224.68]) by mx-prod-int-04.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id C617119560AD; Wed, 2 Oct 2024 15:57:23 +0000 (UTC) From: David Marchand To: dev@dpdk.org Cc: bruce.richardson@intel.com, rjarry@redhat.com, ktraynor@redhat.com Subject: [PATCH 0/2] Fix race in ethdev telemetry Date: Wed, 2 Oct 2024 17:57:06 +0200 Message-ID: <20241002155709.2522273-1-david.marchand@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.40 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true 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 Following a discussion we had during the summit, here is one series to fix a race between an application thread and the telemetry thread handling requests on ethdev ports. The problem may be generic to other device classes providing telemetry callbacks, but for now, this series goes with a simple and naive approach of putting locks in the ethdev layer. Comments welcome. -- David Marchand David Marchand (2): ethdev: expose telemetry dump command for Windows ethdev: fix race on ports for telemetry commands lib/ethdev/rte_ethdev_telemetry.c | 105 ++++++++++++++++++------------ 1 file changed, 65 insertions(+), 40 deletions(-) -- 2.46.2