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 6DE1CA00C5; Thu, 15 Sep 2022 18:57:40 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 12F6D4021D; Thu, 15 Sep 2022 18:57:40 +0200 (CEST) Received: from mail-ej1-f47.google.com (mail-ej1-f47.google.com [209.85.218.47]) by mails.dpdk.org (Postfix) with ESMTP id 817F740156 for ; Thu, 15 Sep 2022 18:57:38 +0200 (CEST) Received: by mail-ej1-f47.google.com with SMTP id d1so2754303eje.8 for ; Thu, 15 Sep 2022 09:57:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date; bh=K/Jwklil+ltL2QCxv27BCc8un75FpSXgbtIAs63JyQ8=; b=DStQygQieMDmmHKE9sGCowrrV7qYf3vzqLTqnzg7Z/OZsjrmGXHxCkmbFR8EmA5dew WssdEA5br09STZlFFN3jWLbyUwhBtHAYgGXzi5FIpgs893wAZ7h3oNxAuaBAmcPrHwFQ 3Zo5k8yWD2AwjmZbu9vFsr+Qp8fA467FkicNORH7lpuBjtbIQp5IY0CH/kDeXztStWGf 6wbtUUW3O8JQ9IGGMo7wo8IwC5aaEUfRIs1e/a7tVxqqUyh5douFxZZj4EuJaL4m7DET bsk31YmVI1tvmAH2XXt1PhxB199usGw442ztXpQ7lgI4MCpBA2XwL3Wb9KYiZaWwClcG 6Sgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date; bh=K/Jwklil+ltL2QCxv27BCc8un75FpSXgbtIAs63JyQ8=; b=Zu0qu+MACSwamBZ3Ff4J1t7c8SQUjHPY09/HVlyJ8eYGUnxuqaoeTWUOfgbChswV1G t05ukJOkGMOndzp7nf+MAQGxPdpTLdQEvLZuAk3HALcg9TR8bpTFCVMVPMBHvW09+WTX IYfy9qwcsRe6ACyhL58I30AupzUYajml5P6FzjdBy7H9ZD3UAm1AKnGkT85cNIS6iMk7 K//9Y0MWBg31eEYkJKTU136DdBO63evROYXW0kS9UH6jEvFMwJeTsSl5cmwwgf6qkD+X 2fjcbGBQAV1FzRWde3FJwNGK69nmjg7OzE9PNiLUs0jk81e1VRcFF6YdP97yo6fspRt9 3BvA== X-Gm-Message-State: ACrzQf24he4rnlUQpvCKYpy+2Gg5eR6tcAUDym1NwlyZA6OfehEKnf+n wbtFhdnMOcYCYIbwSz7tWkWB7RYohiLqLaRgiVpmW+B5ARY= X-Google-Smtp-Source: AMsMyM4r0/SuU/qbMSSjHAAmoAFcr38KlKz/FlgX/bn+ajTWuQxiJaRFjFyTQV/QRmUQLIs72ykBpSD7p4z6G/qFrPk= X-Received: by 2002:a17:907:1b1a:b0:74a:18f7:7f63 with SMTP id mp26-20020a1709071b1a00b0074a18f77f63mr679840ejc.28.1663261057802; Thu, 15 Sep 2022 09:57:37 -0700 (PDT) MIME-Version: 1.0 From: Kamaraj P Date: Thu, 15 Sep 2022 22:27:25 +0530 Message-ID: Subject: Cannot set affinity - pthread_setaffinity_np - DPDK21 To: dev Content-Type: multipart/alternative; boundary="00000000000084e5cb05e8ba249d" 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 --00000000000084e5cb05e8ba249d Content-Type: text/plain; charset="UTF-8" Hi Team, There are lot of discussion about below code: rte_panic("Cannot set affinity %d i %d threadid %d\n", ret, i, lcore_config[i].thread_id); Is there any guildiness(or patch) from the DPDK community about avoiding these panic messages in our DPDK application ? Even if we remove the panic to replace the warning , will it lead to any impact ? Please suggest. Thanks, Kamaraj --00000000000084e5cb05e8ba249d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,=C2=A0

There are lot of discuss= ion about below code:
=C2=A0rte_panic("Cannot set affinity %= d i %d threadid %d\n", ret, i, lcore_config[i].thread_id);

Is there any guildiness(or patch) from the DPDK community= about avoiding these panic messages in our DPDK application ? Even if we r= emove the panic to replace the warning , will it lead to any impact ?=C2=A0=

Please suggest.=C2=A0

Thanks,
Ka= maraj
--00000000000084e5cb05e8ba249d--