DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kamaraj P <pkamaraj@gmail.com>
To: dev <dev@dpdk.org>
Subject: Cannot set affinity - pthread_setaffinity_np - DPDK21
Date: Thu, 15 Sep 2022 22:27:25 +0530	[thread overview]
Message-ID: <CAG8PAapuyoD9g-KYHf06ZxZbfGpOT_h-Z5WjVg=oLc6EBtV-uA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 385 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 526 bytes --]

             reply	other threads:[~2022-09-15 16:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 16:57 Kamaraj P [this message]
2022-09-16  4:07 ` Kamaraj P
2022-09-16 15:13   ` Stephen Hemminger
2022-09-18 16:35     ` Kamaraj P
2022-09-19 17:04       ` Stephen Hemminger
2022-09-20 13:26         ` Kamaraj P

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG8PAapuyoD9g-KYHf06ZxZbfGpOT_h-Z5WjVg=oLc6EBtV-uA@mail.gmail.com' \
    --to=pkamaraj@gmail.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).