Mailing List Archive: Linux: Kernel

2.6.17-ck1

Index | Next | Previous | View Threaded

kernel at kolivas

Jun 18, 2006, 12:36 AM

Post #1 of 7 (398 views)
Permalink

2.6.17-ck1

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 cks is available with more emphasis on serverspace.

Apply to 2.6.17
http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.17/2.6.17-ck1/patch-2.6.17-ck1.bz2

or server version
http://www.kernel.org/pub/linux/kernel/people/ck/patches/cks/patch-2.6.17-cks1.bz2

web:
http://kernel.kolivas.org

all patches:
http://www.kernel.org/pub/linux/kernel/people/ck/patches/

Split patches available.

Full patchlist:

sched-implement-smpnice-2.6.17.patch
sched-revise_smt_nice_locking.patch
2.6.17-smpnice-staircase-16.patch
sched-staircase16_interactive_tunable.patch
sched-staircase16_compute_tunable.patch
sched-range.patch
sched-iso-4.5.patch
track_mutexes-1.patch
sched-idleprio-1.9.patch
sched-limit_policy_changes.patch
defaultcfq.diff
cfq-ioprio_inherit_rt_class.patch
cfq-iso_idleprio_ionice.patch
hz-default_1000.patch
hz-no_default_250.patch
sched-add-above-background-load-function.patch
mm-swap_prefetch-32.patch
swsusp-rework-memory-shrinker-rev-2.patch
mm-convert_swappiness_to_mapped.patch
mm-lots_watermark.diff
mm-kswapd_inherit_prio-1.patch
mm-prio_dependant_scan-1.patch
mm-background_scan-1.patch
mm-idleprio_prio.patch
mm-decrease_minimum_dirty_ratio.patch
mm-set_zero_dirty_ratio.patch
mm-filesize_dependant_lru_cache_add.patch
fs-fcache-v2.1.patch
kconfig-expose_vmsplit_option.patch
2.6.17-ck1-version.patch

--
-ck

jengelh at linux01

Jun 18, 2006, 8:06 AM

Post #2 of 7 (380 views)
Permalink

Re: 2.6.17-ck1 [In reply to]

>
>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 cks is available with more emphasis on serverspace.
>
Last time (2.6.17-rc6-ck1), I had a strange experience over the regular
scheduler. When three gccs were competing for time, each of them got a time
window of 1/3 second in which each ran at 99%.
The regular scheduler does it in a way so that each time window is as small
as possible, that is, top shows 33% for each process on low top
udating intervals like 0.1 sec.
This behavior was not observed with 2.6.16-rcX-ck.

Jan Engelhardt
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

kernel at kolivas

Jun 18, 2006, 8:11 AM

Post #3 of 7 (372 views)
Permalink

Re: 2.6.17-ck1 [In reply to]

On Monday 19 June 2006 01:06, Jan Engelhardt wrote:
> >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 cks is available with more emphasis on
> > serverspace.
>
> Last time (2.6.17-rc6-ck1), I had a strange experience over the regular
> scheduler. When three gccs were competing for time, each of them got a time
> window of 1/3 second in which each ran at 99%.
> The regular scheduler does it in a way so that each time window is as small
> as possible, that is, top shows 33% for each process on low top
> udating intervals like 0.1 sec.
> This behavior was not observed with 2.6.16-rcX-ck.

Were you running them SCHED_IDLEPRIO or in compute mode? They would do that.

--
-ck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

jengelh at linux01

Jun 19, 2006, 4:54 AM

Post #4 of 7 (376 views)
Permalink

Re: 2.6.17-ck1 [In reply to]

>
>Were you running them SCHED_IDLEPRIO or in compute mode? They would do that.
>
I have not changed anything, so I presume SCHED_NORMAL.
Unless they have been made SCHED_IDLEPRIO/compute by staircase's logic...

Jan Engelhardt
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

kernel at kolivas

Jun 19, 2006, 5:51 AM

Post #5 of 7 (384 views)
Permalink

Re: 2.6.17-ck1 [In reply to]

On Monday 19 June 2006 21:54, Jan Engelhardt wrote:
> >Were you running them SCHED_IDLEPRIO or in compute mode? They would do
> > that.
>
> I have not changed anything, so I presume SCHED_NORMAL.
> Unless they have been made SCHED_IDLEPRIO/compute by staircase's logic...

No it wouldn't do that.

I've not seen what you describe happening but definitely the timing of
parallelising jobs in 'make' completely changes with cpu scheduler changes
and with I/O scheduler changes.

However if it's purely unrelated cpu bound tasks running and no disk I/O
involved then full timeslices run out at ~114ms at 1000HZ (longer at lower
HZ) so that should be the longest period one task of the same priority could
possibly run before the others do. That sort of timeslice you would not pick
up at .1s interval 'top's but I find 'top' can be very deceiving if its
timing happens to be exactly what the intervals are it can look like only one
thing is running or one thing is stuck at the same priority and so on.

With actual numbers from interbench testing of fully cpu bound tasks (under
what's called benchmarking cpu of Gaming) the average and max scheduling
delays look of the same magnitude as mainline.

--
-ck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

rociobarroso at att

Jun 19, 2006, 10:20 AM

Post #6 of 7 (390 views)
Permalink

Re: [ck] 2.6.17-ck1 [In reply to]

Con Kolivas wrote:
> 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 cks is available with more emphasis on serverspace.
>
> Apply to 2.6.17
> http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.17/2.6.17-ck1/patch-2.6.17-ck1.bz2
>
> or server version
> http://www.kernel.org/pub/linux/kernel/people/ck/patches/cks/patch-2.6.17-cks1.bz2
>
> web:
> http://kernel.kolivas.org
>
> all patches:
> http://www.kernel.org/pub/linux/kernel/people/ck/patches/
>
> Split patches available.
>
> Full patchlist:
>
>
<snip>

Thanks Con.
Good news: 2.6.17 has support for the Winbond W83687thf sensor chip. One
patch less for me.
Bad news: now nvidia 7167 no longer compiles:
*Unknown symbol pm_unregister

Regards,

Hugo

*

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

jengelh at linux01

Jun 19, 2006, 3:25 PM

Post #7 of 7 (395 views)
Permalink

Re: [ck] 2.6.17-ck1 [In reply to]

> <snip>
>
> Thanks Con.
> Good news: 2.6.17 has support for the Winbond W83687thf sensor chip. One patch
> less for me.
> Bad news: now nvidia 7167 no longer compiles:

Well that one is old even.

> *Unknown symbol pm_unregister

Jan Engelhardt
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads