From: Stephen Hemminger <stephen@networkplumber.org>
To: Kamaraj P <pkamaraj@gmail.com>
Cc: Fred.L.Templin@boeing.com, "Burakov,
Anatoly" <anatoly.burakov@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
David Marchand <david.marchand@redhat.com>,
Nageswara Rao Penumarthy <npenumar@cisco.com>, dev <dev@dpdk.org>,
kalas@cisco.com
Subject: Re: Cannot set affinity - pthread_setaffinity_np - DPDK21
Date: Fri, 16 Sep 2022 08:13:13 -0700 [thread overview]
Message-ID: <20220916081313.1680e742@hermes.local> (raw)
In-Reply-To: <CAG8PAaoE8VvjLj7a7j6=y_Zn1GW3sG0OsYux1NkwER7pg3wwSg@mail.gmail.com>
On Fri, 16 Sep 2022 09:37:32 +0530
Kamaraj P <pkamaraj@gmail.com> 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 <pkamaraj@gmail.com> 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.
next prev parent reply other threads:[~2022-09-16 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 16:57 Kamaraj P
2022-09-16 4:07 ` Kamaraj P
2022-09-16 15:13 ` Stephen Hemminger [this message]
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=20220916081313.1680e742@hermes.local \
--to=stephen@networkplumber.org \
--cc=Fred.L.Templin@boeing.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=kalas@cisco.com \
--cc=npenumar@cisco.com \
--cc=pkamaraj@gmail.com \
/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).