From: Con Kolivas <kernel@kolivas.org>
To: linux list <linux-kernel@vger.kernel.org>
Cc: ck list <ck@vds.kolivas.org>
Subject: [ckpatch][0/29] 2.6.17-ck1 patches
Date: Sun, 18 Jun 2006 17:26:16 +1000 [thread overview]
Message-ID: <200606181726.16426.kernel@kolivas.org> (raw)
Here is the patch queue for the patches going into 2.6.17-ck1. Why? People
have expressed interest in knowing what the heck all my patches are so I've
added changelogs and am posting them for perusal.
These patches were designed to improve system responsiveness and interactivity
_but_ are plagued with the fundamental problem that I do not have a way of
measuring their effect and proving they help (except for better interbench
results for the staircase cpu scheduler).
Except for the patches that are already in -mm, these patches are _not_ being
pushed for mainline so please don't review them as such. The lack of some
benchmark to prove they help means I won't pursue mainline inclusion since
the abuse I'll get will probably kill me. Constructive comments, however, are
most welcome :)
--
-ck
reply other threads:[~2006-06-18 7:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200606181726.16426.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.kolivas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox