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 5CD12429AF for ; Fri, 21 Apr 2023 23:35:01 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 22D12410FB; Fri, 21 Apr 2023 23:35:01 +0200 (CEST) Received: from mail-ej1-f42.google.com (mail-ej1-f42.google.com [209.85.218.42]) by mails.dpdk.org (Postfix) with ESMTP id BCC6B406B3 for ; Fri, 21 Apr 2023 23:34:59 +0200 (CEST) Received: by mail-ej1-f42.google.com with SMTP id a640c23a62f3a-94f7a0818aeso295800766b.2 for ; Fri, 21 Apr 2023 14:34:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682112899; x=1684704899; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Ht83ySd8YcJJ1LndqI8n6T7oxAMVkSoKWXTXGPiIqs0=; b=r9UwlvV3W2oSiG3OxYjihhKIGcj9RSBgyQiRPnpVHbZN/mT33qfGHuq2+w53V/iVvx qnd1E4hAnUAd6nSJVEbhyy+4l+kUJS1chfRS+L3/Eqd3ZOOXnf+v0HebgfYuFvsAydfk 7QLi92Zct0Dw+xft9l6J0WC0F8sZ5D5mBZwVeAG1tUb1vLIoja0OvOH62G7alfV86S1V /Fi4y5urS1lFcKW3LX2rTGgM16m6qZtrZcAn134ZqD2v+NeMSPrFlBbzvQEaFtIrFYB8 6iNSoJqk1AMhsh8AFAjzcmuBObR5uiQ37NtQh/g/Cr4OKuP1qJ4euBADKIyWVmHBwUnY 45Ug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682112899; x=1684704899; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Ht83ySd8YcJJ1LndqI8n6T7oxAMVkSoKWXTXGPiIqs0=; b=IyDH+US6hOHQRtp00kyEqRmPZ6NxJio73zx4b4ScYDNwSLCxklQJX5ngyUMB1VUzEP pGe+fj4X44xpNId54581QzuXsPGLHXuGYEHsv+UGSFwK15IVtXEEV6BKrgv1CWcyD3cW SFtZsiLdOBYW1Iv9ukNv2j1Y2i36e6mI83e+yDZyttr9DQnz/9XOqUeXRK+osZvZq06k 2Mys6AX4CZiDTP+Xn5u9Zr+y6wnGXhNnxuApY34K5E0lJWJaPkGo3KhRSZdesB3bvezt tPVtogNp/E/Z3hUzi+RwAF9d+93lAG8A/ZIcTx5cgI/8eLjKvjNptZaeJGI+CjlYveAZ 0GqQ== X-Gm-Message-State: AAQBX9dFUf2lq3vX7QQpGNWiWd4T0v2pIuxtLjS6W0urjYte/rhwCIUq ai3KRJ/3789wTUIz1HpkvBO3kuiZtEUdK7mExDeNtXirq/Xd4Q== X-Google-Smtp-Source: AKy350aYzkEl4ZC2RNUWjcU1j9EeYcqFMKPiljn0047YJgl32ak+4cLCLKE2KrTcsNgm8uFrW6WhAaHs+IzlYKZK6Z4= X-Received: by 2002:a17:907:a061:b0:94f:73db:b390 with SMTP id ia1-20020a170907a06100b0094f73dbb390mr2947085ejc.65.1682112899049; Fri, 21 Apr 2023 14:34:59 -0700 (PDT) MIME-Version: 1.0 From: Antonio Di Bacco Date: Fri, 21 Apr 2023 23:34:48 +0200 Message-ID: Subject: eal-intr-thread, rte_mp_handle threads of secondary running on ISOLATED cores To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org I have a primary process whose eal-intr-thread rte_mp_handle threads are running correctly on "non-isolated" cores. The primary forks a secondary whose eal-intr-thread rte_mp_handle threads are running on "isolated" cores. I'm using DPDK 21.11, I believe this is a bug. What is your opinion? BR, Anna.