From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <users-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C763AA0093 for <public@inbox.dpdk.org>; Tue, 23 Aug 2022 13:57:14 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 50F3C40DDE; Tue, 23 Aug 2022 13:57:14 +0200 (CEST) Received: from mail-oo1-f47.google.com (mail-oo1-f47.google.com [209.85.161.47]) by mails.dpdk.org (Postfix) with ESMTP id 0FBBC40DDA for <users@dpdk.org>; Tue, 23 Aug 2022 13:57:13 +0200 (CEST) Received: by mail-oo1-f47.google.com with SMTP id u5-20020a4a5705000000b0044b34c2c89cso361123ooa.9 for <users@dpdk.org>; Tue, 23 Aug 2022 04:57:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=5EcwLZjf9n6ktAZxnAefKTj3DjfWISIVL6lyczUFRJg=; b=D9s2NaEVpE37JCIdFLQGt/bmBYYdp/9xl021dDlNP9hdRM5ffNi3TXjRwQrcfnF1Hj /ze9fKjnM8W5rZXJsNhPdaecvOwecfukBZDY2vc/VADRwAK1KIM6Q51aFYkjIAWg7X34 GODeJ7YVYJNnLxS2scmFUf109FMoaR3aT2B0HRgHBC0oWtRlEEJTNowKxujO1chBRkCJ 9z3cENFHdXVpfyE6Ub9ag1zZeS2+XBNL7qfyPnsY7AgoKEcfvWyK3uIAeCIyxBgdd/Vj ubTsRjKHGzsre9nxwT/aJX9CDO0SYilWe4eS5YpiUl5OEnZEoC8F/s62TSokxEDJaMuO qSQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=5EcwLZjf9n6ktAZxnAefKTj3DjfWISIVL6lyczUFRJg=; b=14QKrQ7Fj1fObw+T/hkNTnLED6r3aZQpYAaynnQws/PS+qRxKVI96Lvm5raTyLhsLM T1c1W0edVGxeJdpVfL/hWS6/2Ie3jDPQJHb1MDXU3feC6ECOBjyOsz+wjo6hqDEVL8y4 qzYZCSJo/7gH9Ai5YYmJFr48ULA0GTeCxqSLxdr3xlrpCWjhRDMhGQfgSPGMNyln8iRu 682CVgTxkeSp2TDqbJwOX1C2dGrTWXSC0UHkhq8v5jRAyyrfiZ2d0jWFWwKOP9uGEBHB nEZm7DBTLK9JpszioGVEVvXYjVMEfcd5LxR7VqJ3MFjhhMOA8gJHmM+SVE52qmBQBv7g kPbw== X-Gm-Message-State: ACgBeo1l2AmootweatTYXs+CKC8dpIevWTTtasBdKyZ8ulsb7yuwsTyh DsDCxcV6QY8vNE5CTOSkAkdczi6JsqA1jAWNc2cOwVNt X-Google-Smtp-Source: AA6agR44BMZm02ESlmAc1YuBJ7jcHgR/gM+aSo4uP/5Ssa6D6xae0OuZpsIGOAFxEhaDUM4SXQCzvlOX08/Lun3L7RQ= X-Received: by 2002:a05:6820:541:b0:44a:907d:c641 with SMTP id n1-20020a056820054100b0044a907dc641mr7850890ooj.65.1661255832317; Tue, 23 Aug 2022 04:57:12 -0700 (PDT) MIME-Version: 1.0 References: <CAO8pfFnekCRktTBLPdbVwUrpsphqmMRsEOg-fQkYMRPDz9XgaQ@mail.gmail.com> <20220823132245.5a9f9876@sovereign> In-Reply-To: <20220823132245.5a9f9876@sovereign> From: Antonio Di Bacco <a.dibacco.ks@gmail.com> Date: Tue, 23 Aug 2022 13:57:01 +0200 Message-ID: <CAO8pfFnnHzpDgNd2X98ZzYBBqi75-7g4rzL=bGTFQJoAsuJB1Q@mail.gmail.com> Subject: Re: Can a DPDK API like rte_eth_dev_set_mtu be called by a normal pthread To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions <users.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/users>, <mailto:users-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/users/> List-Post: <mailto:users@dpdk.org> List-Help: <mailto:users-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/users>, <mailto:users-request@dpdk.org?subject=subscribe> Errors-To: users-bounces@dpdk.org Thank you, and what if the pthread is launched by a secondary DPDK process? Should rte_eth_dev_set_mtu be working ? Because I'm observing a crash. On Tue, Aug 23, 2022 at 12:22 PM Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> wrote: > > 2022-08-23 11:25 (UTC+0200), Antonio Di Bacco: > > I have a DPDK process that also creates a normal pthread, is there > > anything wrong to call a DPDK api from this normal pthread? > > Nothing wrong, this is allowed. > > You may be interested in rte_thread_register(), > if you want to consider this thread as an lcore. > Also, rte_socket_id() will return SOCKET_ID_ANY > unless the thread is registered, for example.