From: Pavel Machek <pavel@ucw.cz>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] SCHED_SOFTRR linux scheduler policy ...
Date: Sun, 13 Jul 2003 13:50:33 +0200 [thread overview]
Message-ID: <20030713115033.GA371@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.55.0307091929270.4625@bigblue.dev.mcafeelabs.com>
Hi!
> I finally found a couple of hours for this and I also found a machine were
> I can run 2.5, since luck abandoned myself about this. The small page
> describe the obvious and contain the trivial patch and the latecy test app :
>
> http://www.xmailserver.org/linux-patches/softrr.html
What happens if evil user forks 60 processes, marks them all
SCHED_SOFTRR, and tries to starve everyone else?
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-07-13 11:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 2:33 [patch] SCHED_SOFTRR linux scheduler policy Davide Libenzi
2003-07-13 11:50 ` Pavel Machek [this message]
2003-07-13 11:53 ` Alan Cox
2003-07-13 18:13 ` Scheduler woes ( was [patch] SCHED_SOFTRR linux scheduler policy) Davide Libenzi
2003-07-13 16:08 ` [patch] SCHED_SOFTRR linux scheduler policy Davide Libenzi
-- strict thread matches above, loose matches on Subject: below --
2003-07-12 13:43 Miguel Freitas
2003-07-12 15:20 ` Davide Libenzi
2003-07-12 15:49 ` Jamie Lokier
2003-07-12 15:59 ` Davide Libenzi
2003-07-12 16:20 ` Jamie Lokier
2003-07-12 16:18 ` Davide Libenzi
2003-07-12 16:41 ` Miguel Freitas
2003-07-12 18:51 ` Jamie Lokier
2003-07-13 1:44 ` Davide Libenzi
2003-07-13 14:11 ` Jamie Lokier
2003-07-13 17:15 ` Davide Libenzi
2003-07-12 22:42 ` Bill Huey
2003-07-13 2:39 ` Davide Libenzi
2003-07-13 3:59 ` Bill Huey
2003-07-12 16:34 ` Miguel Freitas
2003-07-12 16:30 ` Davide Libenzi
2003-07-12 19:13 ` Miguel Freitas
2003-07-12 20:07 ` Davide Libenzi
2003-07-12 18:44 ` Jamie Lokier
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=20030713115033.GA371@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=davidel@xmailserver.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.