From: "Karthik Singaram Lakshmanan" <karthiksingaram@gmail.com>
To: linux-rt-users@vger.kernel.org
Subject: Question regarding sched_setaffinity
Date: Sun, 31 Aug 2008 23:12:55 -0400 [thread overview]
Message-ID: <1ca41c0f0808312012v4c52576cw307929992781eeca@mail.gmail.com> (raw)
Hi,
I am a noob to SMP real-time scheduling in linux, I have a question of
sched_setaffinity(). If I restrict an application to a single CPU
using the appropriate cpumask for sched_setaffinity(), Is it
guaranteed that the kernel will never schedule it on any other CPU? I
am asking this because looking at kernel/sched.c seems to use
cpu_clear during load balancing. I am interested in knowing whether the
cache will be invalidated when my task is assigned to a single CPU.
Are there exceptions where the cpu-mask will be overridden?
Thanks for taking the time to answer my query.
Thanks,
Karthik
next reply other threads:[~2008-09-01 3:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 3:12 Karthik Singaram Lakshmanan [this message]
2008-09-05 19:24 ` Question regarding sched_setaffinity Steven Rostedt
2008-09-05 20:04 ` Mark Hounschell
2008-09-05 20:28 ` Steven Rostedt
2008-09-05 20:45 ` Steven Rostedt
2008-09-08 12:28 ` Mark Hounschell
2008-09-08 14:40 ` Karthik Singaram Lakshmanan
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=1ca41c0f0808312012v4c52576cw307929992781eeca@mail.gmail.com \
--to=karthiksingaram@gmail.com \
--cc=linux-rt-users@vger.kernel.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).