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 5624D429B7 for <public@inbox.dpdk.org>; Sat, 22 Apr 2023 18:08:52 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B8FB64021D; Sat, 22 Apr 2023 18:08:51 +0200 (CEST) Received: from mail-pf1-f172.google.com (mail-pf1-f172.google.com [209.85.210.172]) by mails.dpdk.org (Postfix) with ESMTP id 0BA4B40144 for <users@dpdk.org>; Sat, 22 Apr 2023 18:08:50 +0200 (CEST) Received: by mail-pf1-f172.google.com with SMTP id d2e1a72fcca58-63b5c830d5eso2621431b3a.2 for <users@dpdk.org>; Sat, 22 Apr 2023 09:08:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20221208.gappssmtp.com; s=20221208; t=1682179730; x=1684771730; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=aZlGUKw+3LOnxQEKQQa8l3zEwBEbMBv34x05p5ZA3H0=; b=1iUQH7x5A7QxFCNP7ghLYafOwMN/gPx284pfT9AUuS5fYA3gYA3l5kN1+Yal5hha6Q 5KDTGxNu3Xy3PgTdfO+iXB4gTMOQT7ti/mKkoEWPDXgSqBkyBocf3078BQ6ox8kjXlde 1zkyuleYPrNsDLgZsBFRtDdMYHYJ0AuAlQ8fFH2XvUDCKHSyt4jyYmYrXGyNlCbPd6uH cs7OD5UEf+meQsyYrvRTxSswtqct1DMp9J1ek2P5IBzFLYt2Olzu3rwdK2bKqSzJ1oz5 o2NJqeKP/68Y6PrtBARIK1VhOHAL2bIVWCi9CqBAfDt95tvVpJYQpL1fn7MztbnldaZr RO5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682179730; x=1684771730; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=aZlGUKw+3LOnxQEKQQa8l3zEwBEbMBv34x05p5ZA3H0=; b=Z12ZMKE177EKHxfEQVDs221G0AUt+Q+SaLbg2iffOGkmTDWBhEnySD/1BMdf6XTElA PINIU/b70EoyHhyo/C+B2rJbkUpFEXmjjC2EGFpNNbfERLmuGuczNDOXWI3RxHuiQ7tF /umKyk67ufGCYnMZvkaJ45ip9k4SpzKBlOTV6MQZBtPYHimFNnXh3GC9VexViOmOqoZh i10BFb94AKv045FaSTujIwbUi6zGRkbY2Hdy6x1M8PziHg8rquy2fAZs93Ax+lOoRWZp 4xxsVaSGiFayf3W/G3e8VdhaDFsDzagmgyUGBs7KQkB3paaavjuKEPuRzbg3/0VMyIu3 gTtg== X-Gm-Message-State: AAQBX9cog51W5MCBueqsx/WIPs9WS8t4gr4LRSXCipDLSoyxRL48lWQ2 3oR+IuI7+qdo10uO7/D9x+LsFQ== X-Google-Smtp-Source: AKy350bTZNtWwDQUdQK+/tg3AN7PqB7AnlT2qwV3kkcxdpK6/DKg1qx8zstT6xaEirq1YuykMN6xSw== X-Received: by 2002:a05:6a00:2396:b0:63f:1adb:bf61 with SMTP id f22-20020a056a00239600b0063f1adbbf61mr7664477pfc.18.1682179729844; Sat, 22 Apr 2023 09:08:49 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id u10-20020a62d44a000000b00637ca3eada8sm4691286pfl.6.2023.04.22.09.08.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 22 Apr 2023 09:08:49 -0700 (PDT) Date: Sat, 22 Apr 2023 09:08:47 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: Antonio Di Bacco <a.dibacco.ks@gmail.com> Cc: users@dpdk.org Subject: Re: eal-intr-thread, rte_mp_handle threads of secondary running on ISOLATED cores Message-ID: <20230422090847.09880fc6@hermes.local> In-Reply-To: <CAO8pfFkrhTHvn8fe13Vv99jj=nSF=suN20ei0w034bajVbEAFQ@mail.gmail.com> References: <CAO8pfFkrhTHvn8fe13Vv99jj=nSF=suN20ei0w034bajVbEAFQ@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Fri, 21 Apr 2023 23:34:48 +0200 Antonio Di Bacco <a.dibacco.ks@gmail.com> wrote: > 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. This email is missing lots of info. 1. What is the bug you are seeing, what is the log? 2. Why are you trying to start DPDK in non-standard way? Don't try and be creative and do things in new and different ways unless you are trying to find new and different bugs!