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 2EE5F42D74 for ; Tue, 27 Jun 2023 20:20:42 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CD12840F18; Tue, 27 Jun 2023 20:20:40 +0200 (CEST) Received: from mail-ej1-f48.google.com (mail-ej1-f48.google.com [209.85.218.48]) by mails.dpdk.org (Postfix) with ESMTP id 1F4C740EE1 for ; Tue, 27 Jun 2023 20:20:40 +0200 (CEST) Received: by mail-ej1-f48.google.com with SMTP id a640c23a62f3a-991da766865so287682866b.0 for ; Tue, 27 Jun 2023 11:20:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687890039; x=1690482039; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=S6+mC+OWOtp0ifqWWH2iPYvJi8T/zk4i4v0nHIMz9qM=; b=ZBJ1NR+/nRtIVJqxW5s2hnigNsjehmq0GsHzGboA7+bOIOviRyu61Lu3X1LL7BmBi9 vGvm4vioVHCgIajBCPunnPqSs1Lds2tEBTCnMGHG742KNFbf8OdBQ48zAnpceIAgcb8p EAExw5PUdYgj9YA2z7yo80AlaPMmSOVv38TT8sMYZFYkYe15G7HldckEwHrY489zxL23 UYi0kwGzuG/GZU1J3wlRWdVNnFA6zmG6UCgw66Y2qTZVa2FJUpQd2Bo0isXZIdLKM4C4 8jA1oUnOYQnycD5eFQ9//mdkkwsaQWHKiptwu92uTCOgpSbIGW6xkDpPsIduRpxvWBCa PJJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687890039; x=1690482039; 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=S6+mC+OWOtp0ifqWWH2iPYvJi8T/zk4i4v0nHIMz9qM=; b=dXuNa8RlO8f9BNTNucMZoMoPbnIoGtItz7WRbkPxfxN0Lm/FNFf+jcIoXARp3Hu75u 9WSjXfbRXA5ANhNvsqQ6JwS6B9cMd1Lz8gKV5pyAS7lZWomO6VEIIgrwWDxG0U3lJzTY MS9M+xyPNX7mlpWDE98qFmzYb8jiJteuGYHpEPso5+jvKlg0haLlk0Tu+5i3H+ZQERp5 g9rHM08HQJRk+JBgCMYZN5ZFlDat9tX7RD8mbquwKJiAujOyiCsOsUQtVPBOz0eK4N/n 69/EQzihWSNZtQrcr6LP3lbMcvVNz66CKvjUwY5euj9d2mS51tIOMS8StgtIaW8VABKa zNCQ== X-Gm-Message-State: AC+VfDy21tFskR3pgrWNul1kSoFS743WR1M2D/qFXWI2zowU9kVeMrYK 7pEXCY6zd2je2mISzCfmr16sCIMc92S/HCgz2cfQGcRyBNbPAw== X-Google-Smtp-Source: ACHHUZ5meXE1V8bDvwHXQo5V2OUu0GvQGLj3lXfx5VRKPPzQPLPELW5kBexXCANZYHFmMydnlAernf1Y5QMyHAJ5J/A= X-Received: by 2002:a17:906:1d05:b0:98d:3b40:eecf with SMTP id n5-20020a1709061d0500b0098d3b40eecfmr12336829ejh.4.1687890039501; Tue, 27 Jun 2023 11:20:39 -0700 (PDT) MIME-Version: 1.0 References: <20230625074926.38ea8586@hermes.local> In-Reply-To: <20230625074926.38ea8586@hermes.local> From: Antonio Di Bacco Date: Tue, 27 Jun 2023 20:20:28 +0200 Message-ID: Subject: Re: Multiple rte_launch_remote multiple times on main lcore To: Stephen Hemminger Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org This is very useful. Anyway, just on main_lcore, could I launch many pthreads (with pthread_create) ? Does this interfere with DPDK? On Sun, Jun 25, 2023 at 4:49=E2=80=AFPM Stephen Hemminger wrote: > > On Tue, 20 Jun 2023 17:33:59 +0200 > Antonio Di Bacco wrote: > > > Is it possible to launch multiple threads on the main lcore? > > Who will be in charge of scheduling those threads on the main lcore > > (main lcore is isolated)? > > > > Not the OS I suppose. > > > > Thank you > > If you start trying to add threads like this, it will lead to > all sorts of locking problems. When one thread gets the lock > and then gets preempted by the scheduler and another thread > (bound to same lcore) tries to acquire the lock, it will spin > and wait until the first thread is rescheduled. > > DPDK was designed for dedicated threads per lcore.