From: jos poortvliet <jos@mijnkamer.nl>
To: ck@vds.kolivas.org
Cc: Con Kolivas <kernel@kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] 2.6.19-ck2
Date: Sat, 09 Dec 2006 09:44:41 +0100 [thread overview]
Message-ID: <200612090944.46358.jos@mijnkamer.nl> (raw)
In-Reply-To: <200612091614.30096.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
Op Sat Dec 9 2006, schreef Con Kolivas:
(cut)
> Changes (first significant changes since :
> Added:
> +sched-fix_iso_starvation.patch
> A bug first introduced into 2.6.18-ck1/cks1 meant that SCHED_ISO tasks were
> not being throttled when above their cpu limit. This presents a security
> risk to any machine with user logins and upgrading for this issue should be
> considered a high priority.
>
> +sched-make_softirqd_batch.patch
> Instead of 'nice'ing ksoftirqd we can use the policy hint of SCHED_BATCH
> which specifies it as not requiring low latency. This increases the cpu use
> possible under very heavy softirq traffic (such as network loads) and
> decreases the latency that might otherwise be seen (such as keyboard input
> under heavy cpu load on slow machines).
nice, con, nice! good to see you're back! how are things progressing in the
japanese area?
grtz
Jos
--
Disclaimer:
Alles wat ik doe denk en zeg is gebaseerd op het wereldbeeld wat ik nu heb.
Ik ben niet verantwoordelijk voor wijzigingen van de wereld, of het beeld wat
ik daarvan heb, noch voor de daaruit voortvloeiende gedragingen van mezelf.
Alles wat ik zeg is aardig bedoeld, tenzij expliciet vermeld.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-12-09 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 5:14 2.6.19-ck2 Con Kolivas
2006-12-09 8:44 ` jos poortvliet [this message]
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=200612090944.46358.jos@mijnkamer.nl \
--to=jos@mijnkamer.nl \
--cc=ck@vds.kolivas.org \
--cc=kernel@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
all inboxes | Powered by JetHome®