From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Jon Masters <jcm@redhat.com>,
Michal Schmidt <mschmidt@redhat.com>,
linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Subject: Re: [PATCH] kthread: run kthreadd with max priority SCHED_FIFO
Date: Sat, 22 Dec 2007 02:52:28 -0800 [thread overview]
Message-ID: <20071222025228.02905a01.akpm@linux-foundation.org> (raw)
In-Reply-To: <1198319970.5509.10.camel@homer.simson.net>
On Sat, 22 Dec 2007 11:39:30 +0100 Mike Galbraith <efault@gmx.de> wrote:
>
> On Sat, 2007-12-22 at 04:52 -0500, Jon Masters wrote:
>
> > So, user tasks running with SCHED_FIFO should be able to lock a system?
> > I guess I see both sides of this argument - yes, it's userspace at
> > fault, but in other cases when userspace is at fault, we take action
> > (OOM, segfault, others). Isn't this situation just another case where
> > the kernel needs to avoid the evils of userland going awry?
>
> FYI, Ingo queued the below.
>
> http://lkml.org/lkml/2007/10/31/344
>
That's pretty different of course, but rlimit might be a suitable interface
for implementing RLIMIT_MAX_CONTINUOUS_RT_MILLISECONDS.
next prev parent reply other threads:[~2007-12-22 10:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 22:43 [PATCH] kthread: run kthreadd with max priority SCHED_FIFO Michal Schmidt
2007-12-17 23:00 ` Jon Masters
2007-12-22 9:30 ` Andrew Morton
2007-12-22 9:52 ` Jon Masters
2007-12-22 10:11 ` Andrew Morton
2007-12-22 10:18 ` Jon Masters
2007-12-22 10:39 ` Mike Galbraith
2007-12-22 10:52 ` Andrew Morton [this message]
2007-12-22 11:21 ` Jon Masters
2007-12-23 8:50 ` Mike Galbraith
2008-01-07 10:06 ` [PATCH] kthread: always create the kernel threads with normal priority Michal Schmidt
2008-01-07 10:25 ` Andrew Morton
2008-01-07 11:09 ` Ingo Molnar
2008-01-07 17:29 ` Andrew Morton
2008-01-07 17:47 ` Peter Zijlstra
2008-01-08 9:54 ` Michal Schmidt
2008-01-07 13:18 ` Michal Schmidt
2008-01-08 16:22 ` Ingo Molnar
2008-01-07 11:22 ` Remy Bohmer
2008-01-07 13:10 ` Michal Schmidt
2008-01-07 15:53 ` Remy Bohmer
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=20071222025228.02905a01.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=efault@gmx.de \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=takeuchi_satoru@jp.fujitsu.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