Skip to contentSkip to conversation

2.6.12-ck5

DISCUSSION Con Kolivas 4 participants 4 messages Aug 6, 2005

lore
Share & tools
lore
#0 lore raw

These are patches designed to improve system responsiveness and interactivity. It is configurable to any workload but the default ck* patch is aimed at the desktop and ck*-server is available with more emphasis on serverspace.

Apply to 2.6.12 (This includes all patches in 2.6.12.4):
http://ck.kolivas.org/patches/2.6/2.6.12/2.6.12-ck5/patch-2.6.12-ck5.bz2
or for server version:
http://ck.kolivas.org/patches/2.6/2.6.12/2.6.12-ck5/patch-2.6.12-ck5-server.bz2

web:
http://kernel.kolivas.org
all patches:
http://ck.kolivas.org/patches/
Split patches available.

Changes since 2.6.12-ck4:
-schedbatch2.8.diff
+schedbatch2.9.diff
A rare stall on hyperthreading was addressed and now batch tasks suspend properly.

-schediso2.12.diff
SCHED_ISO was dropped entirely. It broke in ck4, and there is now a decent defacto standard for unprivileged realtime in mainline kernel with realtime RLIMITS so I'm supporting the use of that instead.

-isobatch_ionice2.diff
+batch_ionice.diff
Remove check for SCHED_ISO

-HZ-864.diff
It seems there were far more areas of the kernel not ready for this Hz value than I could have anticipated much to my dismay even though all code should be written in a HZ neutral fashion. Return normal -ck to HZ=1000 and change ck-server to HZ=100.

-patch-2.6.12.3
+patch-2.6.12.4.bz2
Latest stable series

-2612ck4-version.diff
+2612ck5-version.diff
Version update.

Cheers,
Con

#1 lore raw
Quoted 3 lines · Con Kolivas

SCHED_ISO was dropped entirely. It broke in ck4, and there is now a decent defacto standard for unprivileged realtime in mainline kernel with realtime RLIMITS so I'm supporting the use of that instead.

Too bad, this was a nice feature, but it seems like a hard problem (even OSX does not really do isochronous scheduling despite when the developer guides say). It would be good to revisit this for 2.7.

Lee

#3 lore raw
In reply to Con Kolivas
Quoted 6 lines · Con Kolivas

-schediso2.12.diff
SCHED_ISO was dropped entirely. It broke in ck4, and there is now a decent defacto standard for unprivileged realtime in mainline kernel with realtime RLIMITS so I'm supporting the use of that instead.

Just a silly question, what will happen if one tries to set SCHED_ISO (with eg schedtool))? will the program just coninue as SCHED_NORM or die by some signal?

(btw, I add myself to the array of people that will miss SCHED_ISO :)

also, how does the RLIMITS work? (ie, how does one set that on a proccess, is it poosible to use schedtool to do that?)

Cheers
Fredrik

Signature · 7 lines
After all, if you are in school to study computer science, then a
professor saying: 
 "use this proprietary software to learn computer science" is the
same as English professor handing you a copy of Shakespeare
and saying:
 "use this book to learn Shakespeare without opening the book itself."
  -- Bradley Kuhn