From: Joe Korty <joe.korty@ccur.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] protect migration/%d etc from sched_setaffinity
Date: Thu, 31 Jul 2003 19:30:51 -0400 [thread overview]
Message-ID: <20030731233050.GE7852@rudolph.ccur.com> (raw)
In-Reply-To: <p73vftinv5c.fsf@oldwotan.suse.de>
On Fri, Aug 01, 2003 at 01:17:34AM +0200, Andi Kleen wrote:
> Joe Korty <joe.korty@ccur.com> writes:
> >
> > diff -Nura linux-2.6.0-test2/include/linux/sched.h.orig linux-2.6.0-test2/include/linux/sched.h
> > --- linux-2.6.0-test2/include/linux/sched.h.orig 2003-07-27 12:57:39.000000000 -0400
> > +++ linux-2.6.0-test2/include/linux/sched.h 2003-07-31 15:52:25.000000000 -0400
> > @@ -488,6 +488,7 @@
> > #define PF_LESS_THROTTLE 0x01000000 /* Throttle me less: I clena memory */
> > #define PF_SYNCWRITE 0x00200000 /* I am doing a sync write */
> > #define PF_READAHEAD 0x00400000 /* I am doing read-ahead */
> > +#define PF_CPULOCK 0x00800000 /* lock users out from changing cpus_allowed */
>
> It would be probably better to just check for ->mm == NULL
>
> This should catch all kernel threads that use daemonize
>
> -Andi
That is what Robert suggested and it is acceptable to me, though suboptimal..it blocks
every daemon, not just the ones that have to be blocked for system survivability.
Joe
next prev parent reply other threads:[~2003-07-31 23:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030731224604.GA24887@tsunami.ccur.com.suse.lists.linux.kernel>
2003-07-31 23:17 ` [PATCH] protect migration/%d etc from sched_setaffinity Andi Kleen
2003-07-31 23:30 ` Joe Korty [this message]
2003-08-01 10:26 Mikael Pettersson
-- strict thread matches above, loose matches on Subject: below --
2003-07-31 22:46 Joe Korty
2003-07-31 22:47 ` Andrew Morton
2003-07-31 23:11 ` Joe Korty
2003-07-31 23:17 ` Andrew Morton
2003-07-31 23:41 ` Robert Love
2003-08-01 0:01 ` Joe Korty
2003-07-31 23:02 ` Robert Love
2003-07-31 23:06 ` Joe Korty
2003-07-31 23:18 ` Robert Love
2003-07-31 23:16 ` Joe Korty
2003-07-31 23:27 ` Robert Love
2003-07-31 23:26 ` Joe Korty
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=20030731233050.GE7852@rudolph.ccur.com \
--to=joe.korty@ccur.com \
--cc=ak@suse.de \
--cc=linux-kernel@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