Re: [patch] CFS scheduler, v4

2007-04-23 Thread Ingo Molnar

* Michael Gerdau <[EMAIL PROTECTED]> wrote:

> > i'm pleased to announce release -v4 of the CFS patchset. The patch 
> > against v2.6.21-rc7 can be downloaded from:
> > 
> > http://redhat.com/~mingo/cfs-scheduler/
> 
> I can't get 2.6.21-rc7-CFS-v4 to boot. Immediately after selecting 
> this kernel I see a very fast scrolling (loop?) sequence of addrs 
> which I don't know how to stop to write them down. They don't appear 
> in any kernel log either. However I see two Tux at the top of the 
> screen.

could you try -v5? It has at least one such bug fixed. (If it still 
happens then please try to make a digital picture of the screen and send 
the picture to me.)

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


Re: [patch] CFS scheduler, v4

2007-04-23 Thread Ingo Molnar

* Michael Gerdau [EMAIL PROTECTED] wrote:

  i'm pleased to announce release -v4 of the CFS patchset. The patch 
  against v2.6.21-rc7 can be downloaded from:
  
  http://redhat.com/~mingo/cfs-scheduler/
 
 I can't get 2.6.21-rc7-CFS-v4 to boot. Immediately after selecting 
 this kernel I see a very fast scrolling (loop?) sequence of addrs 
 which I don't know how to stop to write them down. They don't appear 
 in any kernel log either. However I see two Tux at the top of the 
 screen.

could you try -v5? It has at least one such bug fixed. (If it still 
happens then please try to make a digital picture of the screen and send 
the picture to me.)

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


Re: [patch] CFS scheduler, v4

2007-04-22 Thread Michael Gerdau
> i'm pleased to announce release -v4 of the CFS patchset. The patch 
> against v2.6.21-rc7 can be downloaded from:
> 
> http://redhat.com/~mingo/cfs-scheduler/

I can't get 2.6.21-rc7-CFS-v4 to boot. Immediately after selecting
this kernel I see a very fast scrolling (loop?) sequence of addrs
which I don't know how to stop to write them down. They don't appear
in any kernel log either. However I see two Tux at the top of the
screen.

I'm using the very same .config I also use with 2.6.21-rc7-sd0.x

What could be wrong and how could I track that down ?

FWIW this also happened with 2.6.21-rc7-CFS-v3 and thus for
2.6.21-rc7-CFS-v4 I did a pristine extract of 2.6.20.tar.bz2 and
applied all patches freshly.

System is a Dell XPS M1710, Intel Core2 T7600 2.33, 4GB

Best,
Michael
-- 
 Technosis GmbH, Geschäftsführer: Michael Gerdau, Tobias Dittmar
 Sitz Hamburg; HRB 89145 Amtsgericht Hamburg
 Vote against SPAM - see http://www.politik-digital.de/spam/
 Michael Gerdau   email: [EMAIL PROTECTED]
 GPG-keys available on request or at public keyserver


pgpp4LQ8jBmat.pgp
Description: PGP signature


Re: [patch] CFS scheduler, v4

2007-04-22 Thread Michael Gerdau
 i'm pleased to announce release -v4 of the CFS patchset. The patch 
 against v2.6.21-rc7 can be downloaded from:
 
 http://redhat.com/~mingo/cfs-scheduler/

I can't get 2.6.21-rc7-CFS-v4 to boot. Immediately after selecting
this kernel I see a very fast scrolling (loop?) sequence of addrs
which I don't know how to stop to write them down. They don't appear
in any kernel log either. However I see two Tux at the top of the
screen.

I'm using the very same .config I also use with 2.6.21-rc7-sd0.x

What could be wrong and how could I track that down ?

FWIW this also happened with 2.6.21-rc7-CFS-v3 and thus for
2.6.21-rc7-CFS-v4 I did a pristine extract of 2.6.20.tar.bz2 and
applied all patches freshly.

System is a Dell XPS M1710, Intel Core2 T7600 2.33, 4GB

Best,
Michael
-- 
 Technosis GmbH, Geschäftsführer: Michael Gerdau, Tobias Dittmar
 Sitz Hamburg; HRB 89145 Amtsgericht Hamburg
 Vote against SPAM - see http://www.politik-digital.de/spam/
 Michael Gerdau   email: [EMAIL PROTECTED]
 GPG-keys available on request or at public keyserver


pgpp4LQ8jBmat.pgp
Description: PGP signature


Re: [patch] CFS scheduler, v4

2007-04-21 Thread Gene Heskett
On Saturday 21 April 2007, S.Çağlar Onur wrote:
>21 Nis 2007 Cts tarihinde, Gene Heskett şunları yazmıştı:
>> This one is another keeper IMO, or as we are fond of saying around here,
>> its good enough for the girls I go with.  If this isn't the best one so
>> far, its very very close and I'm getting pickier.  kmail is the only thing
>> that's lagging, and that's just kmail, which I believe is single threaded.
>
>Add +1 for kmail lags (by the way mines are freezes instead of lags, cause i
>cannot use konsole etc. while these happens)
>
>Cheers

yes, you are correct, the composer in particular, or the response to the + key 
for next message, will freeze for the second or maybe 2, that kmail is 
sorting and storing incoming mail.  This is a major problem for users of 
dialup on an auto basis because its frozen for much of the time it takes the 
much slower modem communications to complete, compared to a dsl circuit where 
one can have fetchmail doing the sucking, and handing it off to procmail for 
treatment by spamassassin and its ilk before finally storing the incoming 
mail in /var/spool/mail/gene.  kmail sees none of that background activity at 
all.  They actually run asynchronously here.

kmail then picks that up and sorts it to the correct kmail folder and this 
does cause the lag/freeze while its doing that.

This latter lag/freeze is all I see, but for those that are using kmail to 
directly access their ISP's mailserver(s), this lag/freeze isn't a 1 second 
freeze, but a 10-30 second freeze, and that is truly a cast iron bitch 
version of a PITA.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
VICARIOUSLY experience some reason to LIVE!!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [patch] CFS scheduler, v4

2007-04-21 Thread S.Çağlar Onur
21 Nis 2007 Cts tarihinde, Gene Heskett şunları yazmıştı: 
> This one is another keeper IMO, or as we are fond of saying around here,
> its good enough for the girls I go with.  If this isn't the best one so
> far, its very very close and I'm getting pickier.  kmail is the only thing
> that's lagging, and that's just kmail, which I believe is single threaded. 

Add +1 for kmail lags (by the way mines are freezes instead of lags, cause i 
cannot use konsole etc. while these happens)

Cheers
-- 
S.Çağlar Onur <[EMAIL PROTECTED]>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!


signature.asc
Description: This is a digitally signed message part.


Re: [patch] CFS scheduler, v4

2007-04-21 Thread S.Çağlar Onur
Hi Ingo;

20 Nis 2007 Cum tarihinde, Ingo Molnar şunları yazmıştı: 
> As usual, any sort of feedback, bugreport, fix and suggestion is more
> than welcome,

I tried hard and found another problem for you :)

With Linus's current git + CFSv4 as soon as i start a guest in VirtualBox [1], 
system enters the following loop;

- Whole system freeze ~5 secs.
- System works well ~5 secs
- Whole system freeze ~5 secs.

Again mainline has no issues but its %100 reproducible under CFSv4.

Following "ps aux" and "top" outputs grabbed while system works well, i cannot 
do anything else while system freezes except moving mouse for fun :P

[EMAIL PROTECTED]> ps aux
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 1  0.0  0.0  0 0 ?Ss   22:26   0:00 init [3]
root 2  0.0  0.0  0 0 ?S22:26   0:00 [migration/0]
root 3  0.3  0.0  0 0 ?SN   22:26   0:11 [ksoftirqd/0]
root 4  0.0  0.0  0 0 ?S<   22:26   0:00 [events/0]
root 5  0.0  0.0  0 0 ?S<   22:26   0:00 [khelper]
root 6  0.0  0.0  0 0 ?S<   22:26   0:00 [kthread]
root26  0.0  0.0  0 0 ?S<   22:26   0:00 [kblockd/0]
root27  0.0  0.0  0 0 ?S<   22:26   0:00 [kacpid]
root   124  0.0  0.0  0 0 ?S<   22:26   0:00 [kseriod]
root   137  0.0  0.0  0 0 ?S<   22:26   0:00 [kapmd]
root   145  0.0  0.0  0 0 ?S22:26   0:00 [pdflush]
root   146  0.0  0.0  0 0 ?S22:26   0:00 [pdflush]
root   147  0.0  0.0  0 0 ?S<   22:26   0:00 [kswapd0]
root   148  0.0  0.0  0 0 ?S<   22:26   0:00 [aio/0]
root   802  0.0  0.0  0 0 ?S<   22:26   0:00 [kpsmoused]
root   844  0.0  0.0  0 0 ?S<   22:26   0:00 [ata/0]
root   845  0.0  0.0  0 0 ?S<   22:26   0:00 [ata_aux]
root   856  0.0  0.0  0 0 ?S<   22:26   0:01 [scsi_eh_0]
root   857  0.0  0.0  0 0 ?S<   22:26   0:00 [scsi_eh_1]
root   869  0.0  0.0  0 0 ?S<   22:26   0:00 
[ksuspend_usbd]
root   872  0.0  0.0  0 0 ?S<   22:26   0:00 [khubd]
root   919  0.0  0.0  0 0 ?S<   22:26   0:00 [khpsbpkt]
root   927  0.0  0.0  0 0 ?S<   22:26   0:00 [knodemgrd_0]
root   982  0.0  0.0  0 0 ?S<   22:26   0:00 [xfslogd/0]
root   983  0.0  0.0  0 0 ?S<   22:26   0:00 [xfsdatad/0]
root   985  0.0  0.0  0 0 ?S<   22:26   0:00 [xfsbufd]
root   986  0.0  0.0  0 0 ?S<   22:26   0:00 [xfssyncd]
root  1050  0.0  0.0  0 0 ?S top
top - 23:24:27 up 58 min,  3 users,  load average: 13.59, 13.00, 7.75
Tasks: 102 total,   1 running, 101 sleeping,   0 stopped,   0 zombie
Cpu(s): 99.4%us,  0.4%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.2%hi,  0.0%si,  0.0%st
Mem:   2067672k total,  1935300k used,   132372k free,  288k buffers
Swap:  2096440k total,0k used,  2096440k free,   961236k cached

  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
 6684 caglar20   0  625m 570m  15m S 99.2 28.3   5:56.17 VirtualBox
  844 root   1 -19 000 S  0.2  0.0   0:00.56 ata/0
 6731 caglar20   0  2312 1124  856 R  0.2  0.1   0:00.04 top
1 root  20   0  1608  556  484 S  0.0  0.0   0:00.92 init
2 root  RT   0 000 S  0.0  0.0   0:00.00 migration/0
3 root  39  19 000 S  0.0  0.0   0:11.85 ksoftirqd/0
4 root   1 -19 000 S  0.0  0.0   0:00.07 events/0
5 root   1 -19 000 S  0.0  0.0   0:00.02 khelper
6 root   1 -19 000 S  0.0  0.0   0:00.00 kthread
   26 root   1 -19 000 S  0.0  0.0   0:00.04 kblockd/0
   27 root   1 -19 000 S  0.0  0.0   0:00.00 kacpid
  124 root   1 -19 000 S  0.0  0.0   0:00.00 kseriod
  137 root   1 -19 000 S  0.0  0.0   0:00.00 kapmd
  145 root  20   0 000 S  0.0  0.0   0:00.00 pdflush
  146 root  20   0 000 S  0.0  0.0   0:00.27 pdflush
  147 root   1 -19 000 S  0.0  0.0   0:00.00 kswapd0
  148 root   1 -19 000 S  0.0  0.0   0:00.00 aio/0
  802 root   1 -19 000 S  0.0  0.0   0:00.00 kpsmoused
  845 root   1 -19 000 S  0.0  0.0   0:00.00 ata_aux
  856 root   1 -19 000 D  0.0  0.0   0:01.04 scsi_eh_0
  857 root   1 -19 000 S  0.0  0.0   0:00.00 scsi_eh_1
  869 root   1 -19 000 S  0.0  0.0   0:00.00 ksuspend_usbd
  872 root   1 -19 000 S  0.0  0.0   0:00.00 khubd
  919 root   1 -19 000 S  0.0  0.0   0:00.00 khpsbpkt
  927 root   1 -19 000 S  0.0  0.0   0:00.00 

Re: [patch] CFS scheduler, v4

2007-04-21 Thread Ingo Molnar

* mdew . <[EMAIL PROTECTED]> wrote:

> Any chance of supporting 2.6.20?

okay, it seems it was less work to backport it to v2.6.20 than it was to 
answer all the "where's the v2.6.20 version?" emails ;-) You can 
download the v2.6.20.7 version of CFS from:

http://redhat.com/~mingo/cfs-scheduler/sched-cfs-v4-v2.6.20.7.patch

let me know how well it works for you and how it compares to the vanilla 
scheduler and/or other schedulers you might have tried.

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


Re: [patch] CFS scheduler, v4

2007-04-21 Thread Ingo Molnar

* mdew . [EMAIL PROTECTED] wrote:

 Any chance of supporting 2.6.20?

okay, it seems it was less work to backport it to v2.6.20 than it was to 
answer all the where's the v2.6.20 version? emails ;-) You can 
download the v2.6.20.7 version of CFS from:

http://redhat.com/~mingo/cfs-scheduler/sched-cfs-v4-v2.6.20.7.patch

let me know how well it works for you and how it compares to the vanilla 
scheduler and/or other schedulers you might have tried.

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


Re: [patch] CFS scheduler, v4

2007-04-21 Thread S.Çağlar Onur
Hi Ingo;

20 Nis 2007 Cum tarihinde, Ingo Molnar şunları yazmıştı: 
 As usual, any sort of feedback, bugreport, fix and suggestion is more
 than welcome,

I tried hard and found another problem for you :)

With Linus's current git + CFSv4 as soon as i start a guest in VirtualBox [1], 
system enters the following loop;

- Whole system freeze ~5 secs.
- System works well ~5 secs
- Whole system freeze ~5 secs.

Again mainline has no issues but its %100 reproducible under CFSv4.

Following ps aux and top outputs grabbed while system works well, i cannot 
do anything else while system freezes except moving mouse for fun :P

[EMAIL PROTECTED] ps aux
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 1  0.0  0.0  0 0 ?Ss   22:26   0:00 init [3]
root 2  0.0  0.0  0 0 ?S22:26   0:00 [migration/0]
root 3  0.3  0.0  0 0 ?SN   22:26   0:11 [ksoftirqd/0]
root 4  0.0  0.0  0 0 ?S   22:26   0:00 [events/0]
root 5  0.0  0.0  0 0 ?S   22:26   0:00 [khelper]
root 6  0.0  0.0  0 0 ?S   22:26   0:00 [kthread]
root26  0.0  0.0  0 0 ?S   22:26   0:00 [kblockd/0]
root27  0.0  0.0  0 0 ?S   22:26   0:00 [kacpid]
root   124  0.0  0.0  0 0 ?S   22:26   0:00 [kseriod]
root   137  0.0  0.0  0 0 ?S   22:26   0:00 [kapmd]
root   145  0.0  0.0  0 0 ?S22:26   0:00 [pdflush]
root   146  0.0  0.0  0 0 ?S22:26   0:00 [pdflush]
root   147  0.0  0.0  0 0 ?S   22:26   0:00 [kswapd0]
root   148  0.0  0.0  0 0 ?S   22:26   0:00 [aio/0]
root   802  0.0  0.0  0 0 ?S   22:26   0:00 [kpsmoused]
root   844  0.0  0.0  0 0 ?S   22:26   0:00 [ata/0]
root   845  0.0  0.0  0 0 ?S   22:26   0:00 [ata_aux]
root   856  0.0  0.0  0 0 ?S   22:26   0:01 [scsi_eh_0]
root   857  0.0  0.0  0 0 ?S   22:26   0:00 [scsi_eh_1]
root   869  0.0  0.0  0 0 ?S   22:26   0:00 
[ksuspend_usbd]
root   872  0.0  0.0  0 0 ?S   22:26   0:00 [khubd]
root   919  0.0  0.0  0 0 ?S   22:26   0:00 [khpsbpkt]
root   927  0.0  0.0  0 0 ?S   22:26   0:00 [knodemgrd_0]
root   982  0.0  0.0  0 0 ?S   22:26   0:00 [xfslogd/0]
root   983  0.0  0.0  0 0 ?S   22:26   0:00 [xfsdatad/0]
root   985  0.0  0.0  0 0 ?S   22:26   0:00 [xfsbufd]
root   986  0.0  0.0  0 0 ?S   22:26   0:00 [xfssyncd]
root  1050  0.0  0.0  0 0 ?Ss  22:26   
0:01 /sbin/udevd --daemon
root  2831  0.0  0.0  0 0 ?S   22:26   0:00 [kondemand/0]
root  2993  0.0  0.0  0 0 ?S   22:26   0:00 [tifm/0]
root  3039  0.0  0.0  0 0 ?S   22:26   0:00 [pccardd]
root  3063  0.0  0.0  0 0 ?S   22:26   0:00 [ipw2200/0]
root  3127  0.0  0.0  0 0 ?Ss   22:26   0:00 Comar
root  3278  0.0  0.0  0 0 ?S22:26   0:00 ComarRPC
root  3334  0.0  0.0  0 0 ?Ss   22:26   
0:00 /usr/sbin/syslogd -m 15
root  3338  0.0  0.0  0 0 ?Ss   22:26   
0:00 /usr/sbin/klogd -c 3 -2
root  3340  0.0  0.0  0 0 ?Ss   22:26   
0:00 /sbin/dhcpcd -R -Y -N -t 20 eth1
root  3345  0.0  0.0  0 0 ?Ss   22:26   
0:00 /usr/sbin/acpid -c /etc/acpi/events
dbus  3351  0.0  0.0  0 0 ?Ss   22:26   
0:00 /usr/bin/dbus-daemon --system
root  3354  0.0  0.0  0 0 ?Ss   22:26   
0:00 /usr/sbin/console-kit-daemon
root  3418  0.0  0.0  0 0 ?Ss   22:26   
0:00 /usr/sbin/polkitd
hal   3420  0.0  0.0  0 0 ?Ss   22:26   
0:00 /usr/sbin/hald --daemon=yes --use-syslog
root  3421  0.0  0.0  0 0 ?S22:26   0:00 hald-runner
hal   3432  0.0  0.0  0 0 ?S22:26   0:00 
hald-addon-keyboard: listening on /dev/input/event0
hal   3435  0.0  0.0  0 0 ?S22:26   0:00 
hald-addon-keyboard: listening on /dev/input/event1
hal   3436  0.0  0.0  0 0 ?S22:26   0:00 
hald-addon-keyboard: listening on /dev/input/event2
hal   3437  0.0  0.0  0 0 ?S22:26   0:00 
hald-addon-keyboard: listening on /dev/input/event4
root  3444  0.0  0.0  0 0 tty1 Ss+  22:26   
0:00 /sbin/mingetty --noclear tty1
root  3445  0.0  0.0  0 0 tty2 Ss+  22:26   
0:00 /sbin/mingetty --noclear tty2
root  3446  0.0  0.0  0 0 tty3 Ss+  22:26   
0:00 /sbin/mingetty tty3
root  3447  0.0  0.0  0 0 tty4 Ss+  22:26   
0:00 /sbin/mingetty tty4
root  3448  0.0  0.0  0 0 

Re: [patch] CFS scheduler, v4

2007-04-21 Thread S.Çağlar Onur
21 Nis 2007 Cts tarihinde, Gene Heskett şunları yazmıştı: 
 This one is another keeper IMO, or as we are fond of saying around here,
 its good enough for the girls I go with.  If this isn't the best one so
 far, its very very close and I'm getting pickier.  kmail is the only thing
 that's lagging, and that's just kmail, which I believe is single threaded. 

Add +1 for kmail lags (by the way mines are freezes instead of lags, cause i 
cannot use konsole etc. while these happens)

Cheers
-- 
S.Çağlar Onur [EMAIL PROTECTED]
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!


signature.asc
Description: This is a digitally signed message part.


Re: [patch] CFS scheduler, v4

2007-04-21 Thread Gene Heskett
On Saturday 21 April 2007, S.Çağlar Onur wrote:
21 Nis 2007 Cts tarihinde, Gene Heskett şunları yazmıştı:
 This one is another keeper IMO, or as we are fond of saying around here,
 its good enough for the girls I go with.  If this isn't the best one so
 far, its very very close and I'm getting pickier.  kmail is the only thing
 that's lagging, and that's just kmail, which I believe is single threaded.

Add +1 for kmail lags (by the way mines are freezes instead of lags, cause i
cannot use konsole etc. while these happens)

Cheers

yes, you are correct, the composer in particular, or the response to the + key 
for next message, will freeze for the second or maybe 2, that kmail is 
sorting and storing incoming mail.  This is a major problem for users of 
dialup on an auto basis because its frozen for much of the time it takes the 
much slower modem communications to complete, compared to a dsl circuit where 
one can have fetchmail doing the sucking, and handing it off to procmail for 
treatment by spamassassin and its ilk before finally storing the incoming 
mail in /var/spool/mail/gene.  kmail sees none of that background activity at 
all.  They actually run asynchronously here.

kmail then picks that up and sorts it to the correct kmail folder and this 
does cause the lag/freeze while its doing that.

This latter lag/freeze is all I see, but for those that are using kmail to 
directly access their ISP's mailserver(s), this lag/freeze isn't a 1 second 
freeze, but a 10-30 second freeze, and that is truly a cast iron bitch 
version of a PITA.

-- 
Cheers, Gene
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
VICARIOUSLY experience some reason to LIVE!!
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [patch] CFS scheduler, v4

2007-04-20 Thread mdew .

Any chance of supporting 2.6.20?

On 4/21/07, Ingo Molnar <[EMAIL PROTECTED]> wrote:


i'm pleased to announce release -v4 of the CFS patchset. The patch
against v2.6.21-rc7 can be downloaded from:

http://redhat.com/~mingo/cfs-scheduler/

this CFS release too is mainly about fixing regressions and improving
interactivity, so the rate of change is relatively low:

11 files changed, 136 insertions(+), 72 deletions(-)

in particular the preemption fix could resolve the 'desktop slows down
under IO load' reports and the 'firefox does not switch tabs fast
enough' reports as well. The suspend2 crash and the yield related
Kaffeine hangs should be resolved as well.

Changes since -v3:

 - usability fix: automatic renicing of kernel threads such as keventd,
   OOM tasks and tasks doing privileged hardware access (such as Xorg).
   (This is a substitute for group scheduling until the group scheduling
details have been worked out.)

 - bugfix: buggy yield() caused suspend2 problems

 - preemption fix: it caused desktop app latencies

As usual, any sort of feedback, bugreport, fix and suggestion is more
than welcome,

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


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


Re: [patch] CFS scheduler, v4

2007-04-20 Thread Gene Heskett
On Friday 20 April 2007, Ingo Molnar wrote:
>i'm pleased to announce release -v4 of the CFS patchset. The patch
>against v2.6.21-rc7 can be downloaded from:
>
>http://redhat.com/~mingo/cfs-scheduler/
>
>this CFS release too is mainly about fixing regressions and improving
>interactivity, so the rate of change is relatively low:
>
>11 files changed, 136 insertions(+), 72 deletions(-)
>
>in particular the preemption fix could resolve the 'desktop slows down
>under IO load' reports and the 'firefox does not switch tabs fast
>enough' reports as well. The suspend2 crash and the yield related
>Kaffeine hangs should be resolved as well.
>
>Changes since -v3:
>
> - usability fix: automatic renicing of kernel threads such as keventd,
>   OOM tasks and tasks doing privileged hardware access (such as Xorg).
>   (This is a substitute for group scheduling until the group scheduling
>details have been worked out.)
>
> - bugfix: buggy yield() caused suspend2 problems
>
> - preemption fix: it caused desktop app latencies
>
>As usual, any sort of feedback, bugreport, fix and suggestion is more
>than welcome,

I've been running this one for several hours now, with amanda running in the 
background due a typu in one of my scripts, so now its playing catchup.

This one is another keeper IMO, or as we are fond of saying around here, its 
good enough for the girls I go with.  If this isn't the best one so far, its 
very very close and I'm getting pickier.  kmail is the only thing that's 
lagging, and that's just kmail, which I believe is single threaded.  Even 
with gzip eating 95% of the cpu, graphics animations like the cards in 
patience are moving at at least 80% speed.  Nice, keep this one and use it 
for the reference. 

>   Ingo



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
In order to dial out, it is necessary to broaden one's dimension.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [patch] CFS scheduler, v4

2007-04-20 Thread Gene Heskett
On Friday 20 April 2007, Ingo Molnar wrote:
i'm pleased to announce release -v4 of the CFS patchset. The patch
against v2.6.21-rc7 can be downloaded from:

http://redhat.com/~mingo/cfs-scheduler/

this CFS release too is mainly about fixing regressions and improving
interactivity, so the rate of change is relatively low:

11 files changed, 136 insertions(+), 72 deletions(-)

in particular the preemption fix could resolve the 'desktop slows down
under IO load' reports and the 'firefox does not switch tabs fast
enough' reports as well. The suspend2 crash and the yield related
Kaffeine hangs should be resolved as well.

Changes since -v3:

 - usability fix: automatic renicing of kernel threads such as keventd,
   OOM tasks and tasks doing privileged hardware access (such as Xorg).
   (This is a substitute for group scheduling until the group scheduling
details have been worked out.)

 - bugfix: buggy yield() caused suspend2 problems

 - preemption fix: it caused desktop app latencies

As usual, any sort of feedback, bugreport, fix and suggestion is more
than welcome,

I've been running this one for several hours now, with amanda running in the 
background due a typu in one of my scripts, so now its playing catchup.

This one is another keeper IMO, or as we are fond of saying around here, its 
good enough for the girls I go with.  If this isn't the best one so far, its 
very very close and I'm getting pickier.  kmail is the only thing that's 
lagging, and that's just kmail, which I believe is single threaded.  Even 
with gzip eating 95% of the cpu, graphics animations like the cards in 
patience are moving at at least 80% speed.  Nice, keep this one and use it 
for the reference. 

   Ingo



-- 
Cheers, Gene
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
In order to dial out, it is necessary to broaden one's dimension.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [patch] CFS scheduler, v4

2007-04-20 Thread mdew .

Any chance of supporting 2.6.20?

On 4/21/07, Ingo Molnar [EMAIL PROTECTED] wrote:


i'm pleased to announce release -v4 of the CFS patchset. The patch
against v2.6.21-rc7 can be downloaded from:

http://redhat.com/~mingo/cfs-scheduler/

this CFS release too is mainly about fixing regressions and improving
interactivity, so the rate of change is relatively low:

11 files changed, 136 insertions(+), 72 deletions(-)

in particular the preemption fix could resolve the 'desktop slows down
under IO load' reports and the 'firefox does not switch tabs fast
enough' reports as well. The suspend2 crash and the yield related
Kaffeine hangs should be resolved as well.

Changes since -v3:

 - usability fix: automatic renicing of kernel threads such as keventd,
   OOM tasks and tasks doing privileged hardware access (such as Xorg).
   (This is a substitute for group scheduling until the group scheduling
details have been worked out.)

 - bugfix: buggy yield() caused suspend2 problems

 - preemption fix: it caused desktop app latencies

As usual, any sort of feedback, bugreport, fix and suggestion is more
than welcome,

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


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