From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] O17int
Date: Tue, 19 Aug 2003 18:39:22 +0200 [thread overview]
Message-ID: <yw1xn0e5lhz9.fsf@users.sourceforge.net> (raw)
In-Reply-To: 200308200102.04155.kernel@kolivas.org
Con Kolivas <kernel@kolivas.org> writes:
> Food for the starving masses.
>
> This patch prevents any single task from being able to starve the
> runqueue that it's on. This minimises the impact a poorly behaved
> application or a malicious one has on the rest of the system. If an
I have to disagree. Open a file of a few hundred lines in XEmacs and
do a regexp search for "^[> ]*-*\n\\([> ]*.*\n\\)*[> ]*foo". The
system will more or less freeze. It's a very nasty regexp, and it's
an error to try to use it, but it still shouldn't freeze the system.
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-08-19 17:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 15:01 [PATCH] O17int Con Kolivas
2003-08-19 16:39 ` Måns Rullgård [this message]
2003-08-20 1:23 ` Con Kolivas
2003-08-20 9:19 ` Måns Rullgård
2003-08-19 18:58 ` Måns Rullgård
2003-08-20 1:19 ` Con Kolivas
2003-08-20 8:53 ` Måns Rullgård
2003-08-20 16:27 ` Wiktor Wodecki
2003-08-20 16:42 ` Nick Piggin
2003-08-20 21:23 ` Con Kolivas
2003-08-21 5:26 ` Con Kolivas
2003-08-21 7:53 ` Mike Galbraith
2003-08-21 11:46 ` Con Kolivas
2003-08-21 15:14 ` Mike Galbraith
2003-08-21 22:18 ` Wes Janzen
2003-08-22 0:09 ` Con Kolivas
2003-08-22 21:17 ` Wes Janzen
2003-08-22 0:42 ` Felipe Alfaro Solana
2003-08-22 5:34 ` Mike Galbraith
2003-08-22 20:48 ` Wes Janzen
2003-08-21 23:59 ` Con Kolivas
2003-08-22 5:11 ` Mike Galbraith
2003-08-21 5:30 ` Apurva Mehta
-- strict thread matches above, loose matches on Subject: below --
2003-08-20 4:55 Voluspa
2003-08-20 8:00 ` Mike Galbraith
2003-08-20 11:21 ` Con Kolivas
2003-08-20 22:51 Voluspa
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=yw1xn0e5lhz9.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.net \
--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.