From: Mike Fedyk <mfedyk@matchmail.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
gaxt <gaxt@rogers.com>, Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH] O16int for interactivity
Date: Fri, 15 Aug 2003 14:01:11 -0700 [thread overview]
Message-ID: <20030815210111.GP1027@matchmail.com> (raw)
In-Reply-To: <200308160149.29834.kernel@kolivas.org>
On Sat, Aug 16, 2003 at 01:49:06AM +1000, Con Kolivas wrote:
> Changes:
> Waker is now kept track of.
>
> Only user tasks have the bonus ceiling from uninterruptible sleep.
>
> Preemption of tasks at the same level with twice as much timeslice has been
> dropped as this is not necessary with timeslice granularity (may improve
> performance of cpu intensive tasks).
>
> Preemption of user tasks is limited to those in the interactive range; cpu
> intensive non interactive tasks can run out their full timeslice (may also
> improve cpu intensive performance)
>
> Tasks cannot preempt their own waker.
>
> Cleanups etc.
Con, given the problems reported, maybe each of these should be in a
different changeset (OXXint, etc...).
Seeing the large number of changes, compared to previous releases gave me a
pause on this patch. So I waited a few minutes and there was a problem
report quickly.
Is there any way you can provide each change in a seperate patch, so we can
narrow down the problem patch? (I have a feeling that most of your changes will do a
lot of good)
Mike
next prev parent reply other threads:[~2003-08-15 21:01 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 15:49 [PATCH] O16int for interactivity Con Kolivas
2003-08-15 18:26 ` Timothy Miller
2003-08-15 18:45 ` Richard B. Johnson
2003-08-16 2:31 ` Con Kolivas
2003-08-18 15:46 ` Timothy Miller
2003-08-18 15:43 ` Nick Piggin
2003-08-18 19:48 ` Timothy Miller
2003-08-18 22:46 ` Nick Piggin
2003-08-15 19:00 ` Felipe Alfaro Solana
2003-08-16 2:14 ` [PATCH]O16.1int was " Con Kolivas
2003-08-15 21:01 ` Mike Fedyk [this message]
2003-08-15 23:03 ` Scheduler activations (IIRC) question Jamie Lokier
2003-08-15 23:54 ` Mike Fedyk
2003-08-16 0:54 ` Jamie Lokier
2003-08-16 6:14 ` Mike Galbraith
2003-08-16 14:18 ` Jamie Lokier
2003-08-17 5:51 ` Mike Galbraith
2003-08-17 6:55 ` Jamie Lokier
2003-08-17 7:05 ` Nick Piggin
2003-08-17 8:34 ` Mike Galbraith
2003-08-17 17:12 ` Jamie Lokier
2003-08-17 17:15 ` Arjan van de Ven
2003-08-17 18:26 ` Jamie Lokier
2003-08-17 18:27 ` Mike Galbraith
2003-08-17 18:29 ` Jamie Lokier
2003-08-17 18:46 ` Jamie Lokier
2003-08-16 20:54 ` Ingo Oeser
2003-08-16 21:39 ` Jamie Lokier
[not found] ` <20030817144203.J670@nightmaster.csn.tu-chemnitz.de>
2003-08-17 20:02 ` Jamie Lokier
2003-08-18 0:23 ` William Lee Irwin III
2003-08-18 10:38 ` Ingo Oeser
2003-08-18 13:09 ` Jamie Lokier
2003-08-16 7:01 ` [PATCH] O16int for interactivity Con Kolivas
2003-08-18 10:08 ` Apurva Mehta
2003-08-18 10:30 ` Con Kolivas
2003-08-18 12:13 ` Apurva Mehta
-- strict thread matches above, loose matches on Subject: below --
2003-08-15 20:50 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=20030815210111.GP1027@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=gaxt@rogers.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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