DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kamaraj P <pkamaraj@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
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: Tue, 20 Sep 2022 18:56:39 +0530	[thread overview]
Message-ID: <CAG8PAapDo8gb57nt8yNDWH3yRUgFj+uMLWT2vL6kA2HO4HZfXQ@mail.gmail.com> (raw)
In-Reply-To: <20220919100403.0f8bd845@hermes.local>

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

Thank you for the clarification.

On Mon, 19 Sep 2022, 10:34 pm Stephen Hemminger, <stephen@networkplumber.org>
wrote:

> On Sun, 18 Sep 2022 22:05:57 +0530
> Kamaraj P <pkamaraj@gmail.com> wrote:
>
> > 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 ?
>
> DPDK doesn't (and shouldn't) know about what cgroups has set.
> You need to align the cgroup and the startup flags of the application.
>

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

      reply	other threads:[~2022-09-20 13:26 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
2022-09-18 16:35     ` Kamaraj P
2022-09-19 17:04       ` Stephen Hemminger
2022-09-20 13:26         ` Kamaraj P [this message]

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=CAG8PAapDo8gb57nt8yNDWH3yRUgFj+uMLWT2vL6kA2HO4HZfXQ@mail.gmail.com \
    --to=pkamaraj@gmail.com \
    --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=stephen@networkplumber.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).