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 16F74A00C3; Sun, 18 Sep 2022 18:36:12 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AB1A44021D; Sun, 18 Sep 2022 18:36:11 +0200 (CEST) Received: from mail-ej1-f43.google.com (mail-ej1-f43.google.com [209.85.218.43]) by mails.dpdk.org (Postfix) with ESMTP id 202A1400D4 for ; Sun, 18 Sep 2022 18:36:10 +0200 (CEST) Received: by mail-ej1-f43.google.com with SMTP id l14so59462227eja.7 for ; Sun, 18 Sep 2022 09:36:10 -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:subject:date; bh=HUiBp6JweurBg/7yvtS/0qgMsaa+Hh8RCcPQBuXUh/o=; b=VfYkrbc1xrkaIE/dAlekB/txco9XIH0ZYs/au4Haj2jBXOPJeisIDV+lBVZzKymiHJ DRamBTwU/nYyw7jyFgSBg8Lcf/8mWOUOQ1oDh6pHfkLbp1KZhWoF82SoU+XB/JF74aVR xQB4i7cHtgfJSQNUtZ5xz9xOfhnwBpH/FrXmsnC75EkZRcwm4AuYsOylf5toPnGkh9IU 0FOE5vytL4zXUhjEiq4BacitPkJNwOB9svZiGfGyK0MRXU4+bacvYofMSSVqgog3dd/0 pGQIHfrmN15Ge7vQ7VLui3067kQShYiMHrqxlFv7CcZJdmrONvz7mJ1SDnrRrP4lAkiC bIhg== 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:subject:date; bh=HUiBp6JweurBg/7yvtS/0qgMsaa+Hh8RCcPQBuXUh/o=; b=1NF4ZNRyqWdTIysxKHqMJmD+e4mKd0cNMma5ZDP9C5R1HAJwJCd5HqYbcqlQK+tCFH 8j9xow4ljk8NtLBsmfpSHxZb3BBLQst4JG0LWASdMhTrOHukPxOI3m9OktNLr5N5+euf gMIT2RUx7J7TMCf3KMchec/R9srGC4JoaUhm8/neFgWHnRvgBkG1EMFpxLQRY7hYto8T nNJHhqayHAlqQjLDQgstkCBPdtGfZvhS7noIZGLRZgGjProOXFzWCNOM3xmFh9qVimD9 U7dSwMAeTEt8imam1WBCtF4vVkfWGjoRGAQY0T9BTJL6mLiMXwlFmEKB8nVigdC7dr4r v4Gw== X-Gm-Message-State: ACrzQf0ETa05XDAxw8LnusuNVWUjpLHsgylnE8G6JMykzEG+CfMjFi7N eYtsqrobP9HgaU0R+H7EozFT4cpyUq8E21rEFw0= X-Google-Smtp-Source: AMsMyM4Gbm4cWG+gWTG9LHDSjJY8ArYpnbLRxmny2VwD6nN+EdJBVf801AtW7jAw2f7a2tdNCPfxSWezlzEaLnlkE38= X-Received: by 2002:a17:906:8a41:b0:780:a367:db50 with SMTP id gx1-20020a1709068a4100b00780a367db50mr8573173ejc.118.1663518969567; Sun, 18 Sep 2022 09:36:09 -0700 (PDT) MIME-Version: 1.0 References: <20220916081313.1680e742@hermes.local> In-Reply-To: <20220916081313.1680e742@hermes.local> From: Kamaraj P Date: Sun, 18 Sep 2022 22:05:57 +0530 Message-ID: Subject: Re: Cannot set affinity - pthread_setaffinity_np - DPDK21 To: Stephen Hemminger Cc: Fred.L.Templin@boeing.com, "Burakov, Anatoly" , Bruce Richardson , David Marchand , Nageswara Rao Penumarthy , dev , kalas@cisco.com Content-Type: multipart/alternative; boundary="000000000000421ccf05e8f63106" 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 --000000000000421ccf05e8f63106 Content-Type: text/plain; charset="UTF-8" Hi Stephen, Yes. The core mask we have aligned to separate cgroup. Probably this might be an issue here. We will change the alignment in our DPDK application. BTW is there a way to check the cores affinity set to DPDK after rte_eail_init ? Do we have to use the taskset command ? Please advise. Thanks, Kamaraj On Fri, Sep 16, 2022 at 8:43 PM Stephen Hemminger < stephen@networkplumber.org> wrote: > On Fri, 16 Sep 2022 09:37:32 +0530 > Kamaraj P wrote: > > > Hi Team, > > Have sent a message to DPDK alias. Can you please have a look and share > > your thoughts on this ? > > Top posting and nag messages just make developers angry > > > > > On Thu, Sep 15, 2022 at 10:27 PM Kamaraj P wrote: > > > > > 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 ? > > Did you check that the core mask passed into the application is valid? > Or that that your application is not running in a container which blocks > access to other CPU's. > --000000000000421ccf05e8f63106 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Stephen,
Yes. The core mask we have aligned to sepa= rate=C2=A0cgroup. Probably this might be an issue here. We will change the = alignment=C2=A0in=C2=A0 our DPDK application.=C2=A0
BTW is there = a way to check the cores affinity set to DPDK after rte_eail_init ? Do we h= ave to use the taskset command ?=C2=A0
Please=C2=A0advise.=C2=A0<= /div>

Thanks,
Kamaraj

On Fri, Sep 16, 202= 2 at 8:43 PM Stephen Hemminger <stephen@networkplumber.org> wrote:
On Fri, 16 Sep 2022 09:37:32 +0530
Kamaraj P <pkama= raj@gmail.com> wrote:

> Hi Team,
> Have sent a message to DPDK alias. Can you please have a look and shar= e
> your thoughts on this ?

Top posting and nag messages just make developers angry

>
> On Thu, Sep 15, 2022 at 10:27 PM Kamaraj P <pkamaraj@gmail.com> wrote:
>
> > Hi Team,
> >
> > There are lot of discussion about below code:
> >=C2=A0 rte_panic("Cannot set affinity %d i %d threadid %d\n&q= uot;, ret, i,
> > lcore_config[i].thread_id);
> >
> > Is there any guildiness(or patch) from the DPDK community about a= voiding
> > these panic messages in our DPDK application ? Even if we remove = the panic
> > to replace the warning , will it lead to any impact ?

Did you check that the core mask passed into the application is valid?
Or that that your application is not running in a container which blocks access to other CPU's.
--000000000000421ccf05e8f63106--