From: Daniel Walker <dwalker@mvista.com>
To: David Rientjes <rientjes@google.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Paul Menage <menage@google.com>, Paul Jackson <pj@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] sched: prevent bound kthreads from changing cpus_allowed
Date: Thu, 05 Jun 2008 13:52:09 -0700 [thread overview]
Message-ID: <1212699129.3319.129.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.1.10.0806051255500.31157@chino.kir.corp.google.com>
On Thu, 2008-06-05 at 12:57 -0700, David Rientjes wrote:
> Kthreads that have called kthread_bind() are bound to specific cpus, so
> other tasks should not be able to change their cpus_allowed from under
> them. Otherwise, it is possible to move kthreads, such as the migration
> or software watchdog threads, so they are not allowed access to the cpu
> they work on.
I'm all for it .. I've crashed test systems just by migrating tasks that
are suppose to stay bound while using cpusets ..
Daniel
next prev parent reply other threads:[~2008-06-05 20:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 19:57 [patch] sched: prevent bound kthreads from changing cpus_allowed David Rientjes
2008-06-05 20:29 ` Paul Jackson
2008-06-05 21:12 ` David Rientjes
2008-06-09 20:59 ` Max Krasnyanskiy
2008-06-09 22:07 ` David Rientjes
2008-06-10 4:23 ` Max Krasnyansky
2008-06-10 17:04 ` David Rientjes
2008-06-10 16:30 ` cpusets and kthreads, inconsistent behaviour Max Krasnyansky
2008-06-10 18:47 ` David Rientjes
2008-06-10 20:44 ` Max Krasnyansky
2008-06-10 20:54 ` David Rientjes
2008-06-10 21:15 ` Max Krasnyansky
2008-06-10 6:44 ` [patch] sched: prevent bound kthreads from changing cpus_allowed Peter Zijlstra
2008-06-10 15:38 ` Max Krasnyansky
2008-06-10 17:00 ` Oleg Nesterov
2008-06-10 17:19 ` Peter Zijlstra
2008-06-10 20:24 ` workqueue cpu affinity Max Krasnyansky
2008-06-11 6:49 ` Peter Zijlstra
2008-06-11 19:02 ` Max Krasnyansky
2008-06-12 18:44 ` Peter Zijlstra
2008-06-12 19:10 ` Max Krasnyanskiy
2008-06-11 16:08 ` Oleg Nesterov
2008-06-11 19:21 ` Max Krasnyansky
2008-06-11 19:21 ` Max Krasnyansky
2008-06-12 16:35 ` Oleg Nesterov
2008-06-11 20:44 ` Max Krasnyansky
2008-06-10 18:00 ` [patch] sched: prevent bound kthreads from changing cpus_allowed Max Krasnyansky
2008-06-05 20:52 ` Daniel Walker [this message]
2008-06-05 21:47 ` Paul Jackson
2008-06-10 10:28 ` Ingo Molnar
2008-06-10 17:47 ` Oleg Nesterov
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=1212699129.3319.129.camel@localhost.localdomain \
--to=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pj@sgi.com \
--cc=rientjes@google.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).