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 984D5428B7; Mon, 3 Apr 2023 12:52:22 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 39E6940ED7; Mon, 3 Apr 2023 12:52:22 +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 D3E3940A7E for ; Mon, 3 Apr 2023 12:52:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680519140; 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=ZvcgryMJgTnFarzTwG7915SbUv7b5kwYTZOLxfXC3pk=; b=foJu1M71s2M9oHoVD442yz9TeFqRxZ4sU185SIjF2iX3cCXV81/k/H56rEKVWkXKM5mYPv PgQnO01vHVOi+RsAuWvldhAJew1oow6aulVPp8Kvr5Gz2/ctXWIMW0/FSH7/WR4aFqP0yz tAapQClso1dvdH+bMkukrkMhpTkwjQY= Received: from mail-pj1-f72.google.com (mail-pj1-f72.google.com [209.85.216.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-27-mxMEmCORPwSORC1JsSIz9w-1; Mon, 03 Apr 2023 06:52:19 -0400 X-MC-Unique: mxMEmCORPwSORC1JsSIz9w-1 Received: by mail-pj1-f72.google.com with SMTP id k4-20020a17090aef0400b0023fcccbd7e6so8855193pjz.5 for ; Mon, 03 Apr 2023 03:52:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680519138; 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=ZvcgryMJgTnFarzTwG7915SbUv7b5kwYTZOLxfXC3pk=; b=CikkAFYcwcdgxhSxrj6E375Tw0qVByiG29fLhaipICIBS7SadfLuQzKXipHNWgeCcZ MSpab6haxlIZzmys5lTiS5gzk4V9VeMvIWloRfKi6xIZSyui6vsnXaJXoXa1erItEXqJ D6Jpfk0S1OMPbAIjvfNrp8b4zKd2QEm1sjrDJHZ1CGvNyo9iQjxVhIlGdLkfwTrso1F+ QP1DdOARDijvDqUdfIintHHFhpG8Tng8wTx4Rm2+rxMf4TJx58avMoWAuV7AE8KKnTu9 akU79jOdSZS3COXq/L9x5OQdFMmLmdNJTygVovHrydy2P4kmgvWzvJ3T94G01jaHTCgu ZdXQ== X-Gm-Message-State: AAQBX9eX8qPPIYdrr4j95vl1C+KrlIyV05MDGqiJcQYk4+VkldbgKZdS FAfkrLUsFaJ6vuS9Gkdunw7AbGRzVT9nDA7i3ab+V76HaClaX0TZEWTHwxs3dzN6c9+lXYMxiIe R4Nb5tBjXA/okIdlNx/c= X-Received: by 2002:a05:6a00:1995:b0:626:2638:5a51 with SMTP id d21-20020a056a00199500b0062626385a51mr18096422pfl.5.1680519138309; Mon, 03 Apr 2023 03:52:18 -0700 (PDT) X-Google-Smtp-Source: AKy350YSM4SLgWL8soKkVW5/OURt7MJmt63lbXKMjDWeBH94Q+OJHCTBSizcbgod7XF2hr/4IJznwn/Wd7JEOVzfhj8= X-Received: by 2002:a05:6a00:1995:b0:626:2638:5a51 with SMTP id d21-20020a056a00199500b0062626385a51mr18096414pfl.5.1680519137951; Mon, 03 Apr 2023 03:52:17 -0700 (PDT) MIME-Version: 1.0 References: <20230224081642.2566619-1-david.marchand@redhat.com> <20230224151143.3274897-1-david.marchand@redhat.com> <095511d4-4fbb-47a8-a8a5-f2a3b932c01f@app.fastmail.com> In-Reply-To: From: David Marchand Date: Mon, 3 Apr 2023 12:52:06 +0200 Message-ID: Subject: Re: [PATCH v2 00/20] Enable lock annotations on most libraries and drivers To: Tyler Retzlaff Cc: dev@dpdk.org, Thomas Monjalon , =?UTF-8?Q?Ga=C3=ABtan_Rivet?= X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Hello Tyler, On Thu, Mar 2, 2023 at 9:52=E2=80=AFAM David Marchand wrote: > On Mon, Feb 27, 2023 at 5:13 PM Ga=C3=ABtan Rivet wrote: > > Ah ok, so if I understand correctly, DPDK would need to declare some > > '__rte_lockable rte_mutex' and associated functions for transparent sup= port, > > to wrap above the pthread API. > > Yes, this is what I had in mind for the mid/long term but it was too > late for 23.03 after -rc1. > > The Windows porting effort will probably need this abstraction too as > we are trying to stop relying on the pthread API. > I don't see this item in Microsoft roadmap, though. Do you have an opinion on this topic? Thanks. --=20 David Marchand