From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>
Subject: [PATCH 0/5] sched - interactivity updates
Date: Fri, 13 Jan 2006 21:22:37 +1100 [thread overview]
Message-ID: <200601132122.39758.kernel@kolivas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
Changes to the kernel over the last few versions have exposed some weaknesses
and quirks in the interactivity estimator. The following 5 patches are aimed
at addressing these issues. Each changes one unique aspect of the
interactivity estimator thus allowing easy comparison if desired.
For those who wish to try them I've placed a simple rolled up patch for
download to apply to 2.6.15 here:
http://ck.kolivas.org/patches/interactivity/2.6.15-O22int.patch
The separate patches are in that directory as well and will follow this email.
Andrew please apply the following 5 patches to -mm for testing.
Cheers,
Con
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-01-13 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 10:22 Con Kolivas [this message]
2006-01-13 11:53 ` [PATCH 0/5] sched - interactivity updates Ingo Molnar
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=200601132122.39758.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.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