From: Shirley Avishour <shirley@imvisiontech.com>
To: Rami Rosen <ramirose@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] running dpdk application on the same machine with other none dpdk application
Date: Wed, 30 Jan 2019 10:27:31 +0200 [thread overview]
Message-ID: <CACn717gGoKQwEejPnycLzsSSTNbd-tUCHeGLhAWEhmEb8Nj1Cg@mail.gmail.com> (raw)
In-Reply-To: <CAHLOa7T_0uB9qh0_a8oHHqr=F7JLf4wKiujoH0FHKNTrA3J_Ug@mail.gmail.com>
Hi Rami,
This is correct but that is because the default value of the PF_NO_SETAFFINITY
flags does not allow to set affinity to kernel threads from user space.
I was looking for a way to change the kernel and recompile it to be able to
block kernel threads from running on the cpu isolated cores. (same as user
space threads).
BR,
Shirley.
On Wed, Jan 30, 2019 at 10:18 AM Rami Rosen <ramirose@gmail.com> wrote:
> Hi Shirley,
>
> > Do you know if the PF_NO_SETAFFINITY flag can help in any way?
>
> AFAIK, this will not work for kernel thread.
>
> For example, with 4.8.13-1 kernel:
> Display all kernel threads with
> ps aux | grep "\["n
>
> (as kernel threads are enclosed in square brackets, [ ])
> And pick one of them and try:
> taskset -pc 7 521
> pid 521's current affinity list: 0-15
> taskset: failed to set pid 521's affinity: Invalid argument
> Regards,
> Rami Rosen
>
>
next prev parent reply other threads:[~2019-01-30 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 16:32 Shirley Avishour
2019-01-30 6:09 ` Rami Rosen
2019-01-30 6:31 ` Shirley Avishour
2019-01-30 6:57 ` Rami Rosen
2019-01-30 7:05 ` Shirley Avishour
2019-01-30 7:26 ` Rami Rosen
2019-01-30 7:47 ` Shirley Avishour
2019-01-30 8:18 ` Rami Rosen
2019-01-30 8:27 ` Shirley Avishour [this message]
2019-01-30 8:30 ` Shirley Avishour
2019-01-30 8:40 ` Rami Rosen
2019-01-30 8:45 ` Shirley Avishour
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=CACn717gGoKQwEejPnycLzsSSTNbd-tUCHeGLhAWEhmEb8Nj1Cg@mail.gmail.com \
--to=shirley@imvisiontech.com \
--cc=dev@dpdk.org \
--cc=ramirose@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).