Minor scheduler fix to get rid of skipping in xmms
Quoted 10 lines · Andrew Morton
That is not clear at this time. We do know that the reaim regression was
introduced by sched-2.6.0-test2-mm2-A3, but we don't know why. Certainly
that patch did not introduce the problem which Andrew's patch fixed. And
we have theorised that Andrew's patch brought back the reaim throughput. And we have extrapolated those observations to possible improvements in volanomark throughput.It's all foggy and I'd like to see a clean rerun of specjbb and volanomark by Mark Peloquin and co, confirming that -mm6 is performing OK.
For specjbb things are looking good from a throughput point of view.
2.6.0-test4 2.6.0-test4-mm6
# of WHs OPs/sec OPs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 9783.46 10093.09 3.16 309.63 293.50 *
4 33783.93 35763.79 5.86 1979.86 1013.52 *
7 54401.52 54288.06 -0.21 -113.46 1632.05
10 56861.59 56445.20 -0.73 -416.39 1705.85
13 56024.86 55720.23 -0.54 -304.63 1680.75
16 43874.77 48994.63 11.67 5119.86 1316.24 *
19 32658.83 31248.04 -4.32 -1410.79 979.76 *But to get these numbers we are using much more CPU. I'll leave it to others to decide if this is good or not.
CPU IDLE TIME
2.6.0-test4 2.6.0-test4-mm6
# of WHs %CPU %CPU %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 87.30 87.31 0.01 0.01 3.62
4 49.53 49.51 -0.04 -0.02 2.49
7 12.40 12.32 -0.65 -0.08 1.37
10 0.36 0.40 11.11 0.04 1.01
13 1.20 0.62 -48.33 -0.58 1.04
16 15.17 2.79 -81.61 -12.38 1.46 *
19 30.66 5.29 -82.75 -25.37 1.92 *Volanomark, on the other hand is still off by quite a bit from test4 stock
Results:Throughput
tolerance = 0.00 + 3.00% of 2.6.0-test4
2.6.0-test4 2.6.0-test4-mm6
Msgs/sec Msgs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 40757 37223 -8.67 -3534.00 1222.71 *Quoted 6 lines
Also, I'm concerned that sched-2.6.0-test2-mm2-A3 caused slowdowns and Andrew's patch caused speedups and they just cancelled out. Let's get Andrew's patch into Linus's tree and see if it speeds things up. If it does, we probably still have a problem.
If thre is any particular patch/tree combination you would like me to try out, please let me know and I will see if I can get the results for you.
Steve
Quoted 5 lines · Steven Pratt
For specjbb things are looking good from a throughput point of view.
...
Volanomark, on the other hand is still off by quite a bit from test4 stock
hmm, thanks.
I'm not sure that volanomark is very representative of any real-world thing.
Quoted 4 lines
...
If thre is any particular patch/tree combination you would like me to try out, please let me know and I will see if I can get the results for you.
Could we please see test5 versus test5 plus Andrew's patch?
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-CAN_MIGRATE_TASK-fix.patch
and if you have time, also test5 plus sched-CAN_MIGRATE_TASK-fix.patch plus
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-balance-fix-2.6.0-test3-mm3-A0.patch
What I'm afraid of is that those patches will yield improved results over test5, and that adding
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-2.6.0-test2-mm2-A3.patch
will slow things down again.
Quoted 3 lines · Andrew Morton
hmm, thanks.
I'm not sure that volanomark is very representative of any real-world thing.
AIUI it's dominated by 3-tier locking issues.
-- wli
Quoted 18 lines · Andrew Morton
Quoted 4 lines · Steven Pratt
For specjbb things are looking good from a throughput point of view.
...
Volanomark, on the other hand is still off by quite a bit from test4 stockhmm, thanks.
I'm not sure that volanomark is very representative of any real-world thing.
Quoted 4 lines
...
If thre is any particular patch/tree combination you would like me to try out, please let me know and I will see if I can get the results for you.Could we please see test5 versus test5 plus Andrew's patch?
Quoted 7 lines
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2
.6.0-test4-mm6/broken-out/sched-CAN_MIGRATE_TASK-fix.patchand if you have time, also test5 plus sched-CAN_MIGRATE_TASK-fix.patch plus
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2
.6.0-test4-mm6/broken-out/sched-balance-fix-2.6.0-test3-mm3-A0.patch
Interestingly enough this drops the volano results the same proportion as Ingo's A3 patch. 11000 ->10400 throughput with same idle, but more schedule().
I've posted some results for test5 volano and test5-A0 here:
http://kernel.kolivas.org/2.5/volano
More testing underway.
Con
Quoted 28 lines · Con Kolivas
Quoted 18 lines · Andrew Morton
Quoted 4 lines · Steven Pratt
For specjbb things are looking good from a throughput point of view.
...
Volanomark, on the other hand is still off by quite a bit from test4 stockhmm, thanks.
I'm not sure that volanomark is very representative of any real-world thing.
Quoted 4 lines
...
If thre is any particular patch/tree combination you would like me to try out, please let me know and I will see if I can get the results for you.Could we please see test5 versus test5 plus Andrew's patch?
Quoted 8 lines
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4 /2
.6.0-test4-mm6/broken-out/sched-CAN_MIGRATE_TASK-fix.patchand if you have time, also test5 plus sched-CAN_MIGRATE_TASK-fix.patch plus
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4 /2
.6.0-test4-mm6/broken-out/sched-balance-fix-2.6.0-test3-mm3-A0.patch
Quoted 8 lines
Interestingly enough this drops the volano results the same proportion as Ingo's A3 patch. 11000 ->10400 throughput with same idle, but more
schedule().I've posted some results for test5 volano and test5-A0 here:
http://kernel.kolivas.org/2.5/volanoMore testing underway.
Correction sorry: These changes were due to sched-CAN_MIGRATE_TASK-fix.patch and the test results say volano-results-2.6.0-test5-A0-*
Con
Quoted 34 lines · Con Kolivas
Quoted 33 lines · Con Kolivas
Quoted 21 lines · Andrew Morton
Quoted 4 lines · Steven Pratt
For specjbb things are looking good from a throughput point of view.
...
Volanomark, on the other hand is still off by quite a bit from test4 stockhmm, thanks.
I'm not sure that volanomark is very representative of any real-world thing.
Quoted 4 lines
...
If thre is any particular patch/tree combination you would like me to try out, please let me know and I will see if I can get the results for you.Could we please see test5 versus test5 plus Andrew's patch?
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-tes t4 /2
.6.0-test4-mm6/broken-out/sched-CAN_MIGRATE_TASK-fix.patchQuoted 6 lines
and if you have time, also test5 plus sched-CAN_MIGRATE_TASK-fix.patch plus
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-tes t4 /2
.6.0-test4-mm6/broken-out/sched-balance-fix-2.6.0-test3-mm3-A0.patchInterestingly enough this drops the volano results the same proportion as Ingo's A3 patch. 11000 ->10400 throughput with same idle, but more
schedule().
Quoted 8 lines
Quoted 4 lines
I've posted some results for test5 volano and test5-A0 here:
http://kernel.kolivas.org/2.5/volanoMore testing underway.
Correction sorry: These changes were due to sched-CAN_MIGRATE_TASK-fix.patch and the test results say volano-results-2.6.0-test5-A0-*
Further testing shows the patch: sched-balance-fix-2.6.0-test3-mm3-A0.patch to have no effect on volano results by itself.
Con
Quoted 7 lines · Con Kolivas
Quoted 4 lines
Correction sorry: These changes were due to sched-CAN_MIGRATE_TASK-fix.patch and the test results say volano-results-2.6.0-test5-A0-*
Further testing shows the patch: sched-balance-fix-2.6.0-test3-mm3-A0.patch to have no effect on volano results by itself.
OK, thanks.
As I have just learnt that volanomark is dominated by sched_yield()-based userspace locking I have suddenly lost all interest in it. We don't want to tune the kernel for braindead locking implementations. Call me when it has been converted to futexes ;)
Do we know what specjbb is doing internally?
Quoted 43 lines · Con Kolivas
Quoted 41 lines · Con Kolivas
Quoted 39 lines · Con Kolivas
Quoted 23 lines · Andrew Morton
Quoted 5 lines · Steven Pratt
For specjbb things are looking good from a throughput point of view.
...
Volanomark, on the other hand is still off by quite a bit from test4 stockhmm, thanks.
I'm not sure that volanomark is very representative of any real-world thing.
Quoted 5 lines
...
If thre is any particular patch/tree combination you would like me to try out, please let me know and I will see if I can get the results for you.Could we please see test5 versus test5 plus Andrew's patch?
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-tes t4 /2
.6.0-test4-mm6/broken-out/sched-CAN_MIGRATE_TASK-fix.patchQuoted 7 lines
and if you have time, also test5 plus sched-CAN_MIGRATE_TASK-fix.patch plus
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-tes t4 /2
.6.0-test4-mm6/broken-out/sched-balance-fix-2.6.0-test3-mm3-A0.patchInterestingly enough this drops the volano results the same proportion as Ingo's A3 patch. 11000 ->10400 throughput with same idle, but more
schedule().I've posted some results for test5 volano and test5-A0 here:
http://kernel.kolivas.org/2.5/volano
Quoted 9 lines
Quoted 6 lines
Quoted 2 lines
More testing underway.
Correction sorry: These changes were due to sched-CAN_MIGRATE_TASK-fix.patch and the test results say volano-results-2.6.0-test5-A0-*
Further testing shows the patch: sched-balance-fix-2.6.0-test3-mm3-A0.patch to have no effect on volano results by itself.
Hi Con,
Any chance you could give this
http://www.kerneltrap.org/~npiggin/v14/sched-rollup-nopolicy-v14.gz
a try? It should apply against test5.
Quoted 4 lines · Nick Piggin
Hi Con,
Any chance you could give this
http://www.kerneltrap.org/~npiggin/v14/sched-rollup-nopolicy-v14.gz
a try? It should apply against test5.
Tested. This patch causes a drop in volano throughput of around 8% also like the other patches. I guess this patch must be good too :P
Con
Quoted 12 lines
Nick Piggin wrote:
Con Kolivas wrote:
Hi Con,
Any chance you could give this
http://www.kerneltrap.org/~npiggin/v14/sched-rollup-nopolicy-v14.gz
a try? It should apply against test5.
I have some STP tests scheduled against this also (PLM 2117) Please let me know if you want other combinations tested - am just catching up on
this thread.
cliffw
Quoted 6 lines
-
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/
Quoted 14 lines · Cliff White
Quoted 14 lines
Nick Piggin wrote:
Con Kolivas wrote:
Hi Con,
Any chance you could give this
http://www.kerneltrap.org/~npiggin/v14/sched-rollup-nopolicy-v14.gz
a try? It should apply against test5.
Quoted 4 lines
I have some STP tests scheduled against this also (PLM 2117) Please let me know if you want other combinations tested - am just catching up on this thread.
cliffw
Thanks Cliff that would be cool. If you could test this: http://www.kerneltrap.org/~npiggin/v14/sched-rollup-v14.gz
as well would be good. The previous one is more important though.
Quoted 15 lines · Nick Piggin
Quoted 12 lines · Cliff White
Quoted 12 lines
Nick Piggin wrote:
Con Kolivas wrote:
Hi Con,
Any chance you could give this
http://www.kerneltrap.org/~npiggin/v14/sched-rollup-nopolicy-v14.gz
a try? It should apply against test5.
Quoted 7 lines
Quoted 4 lines
I have some STP tests scheduled against this also (PLM 2117) Please let me know if you want other combinations tested - am just catching up on this thread.
cliffwThanks Cliff that would be cool. If you could test this: http://www.kerneltrap.org/~npiggin/v14/sched-rollup-v14.gz
as well would be good. The previous one is more important though.
I gave this a try on the same setup that I am using for the regression tests and the scheduler tests for Andrew. What I got was the following oops:
CPU: 5 EIP: 0060:[<c011c577>] Not tainted EFLAGS: 00010003
EIP is at load_balance+0x257/0x3f0
eax: f6583998 ebx: c6099518 ecx: 00000000 edx: c60b9100
esi: c6099518 edi: c60994f8 ebp: f64bff44 esp: f64bff14
ds: 007b es: 007b ss: 0068
Process java (pid: 3482, threadinfo=f64be000 task=f6b13300)
Stack: c6099104 c6098bc0 c6099518 c6099100 00000000 00000005 00000080 000000ff
00000002 f6b13300 c60b9100 c60b8bc0 f64bff8c c011cef9 c60b8bc0
00000001
000000ff f64be000 c60b8bc0 c011ca9d f6b13300 00000000 00000002
c60a8bc0
Call Trace:
[<c011cef9>] schedule+0x4d9/0x550
[<c011ca9d>] schedule+0x7d/0x550
[<c010a08d>] sys_rt_sigsuspend+0xed/0x130
[<c010b01f>] syscall_call+0x7/0xb
Code: 89 19 89 4b 04 8b 47 18 0f ab 42 04 ff 02 89 57 28 8b 55 08Steve
Quoted 3 lines · Steven Pratt
I gave this a try on the same setup that I am using for the regression
tests and the scheduler tests for Andrew. What I got was the following oops:
If you compile your kernel with debugging (-g) turned on, then you can use addr2line on the vmlinux and the eip where it crashed. That is immensely useful in diagnosing oopses. Guessing where load_balance+0x257 is actually located is kinda hard.
Signature · 2 lines
Dave Hansen [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 18 lines · Nick Piggin
Quoted 5 lines · Steven Pratt
Quoted 3 lines · Nick Piggin
Quoted 1 line · Steven Pratt
Quoted 9 lines
Quoted 5 lines
Quoted 1 line
I gave this a try on the same setup that I am using for the regression tests and the scheduler tests for Andrew. What I got was the following oops:
Hi Steven,
This is with the complete sched-rollup-v14.gz or sched-rollup-nopolicy?This is with the complete sched-rollup-v14.gz.
Quoted 6 lines
OK, I've fixed a bug that might be causing that...
Any chance you could grab my new version from:
http://www.kerneltrap.org/~npiggin/v15/
And give it another go. If you get an oops, could you make sure you've compiled with debugging info (-g), and use add2line on vmlinux using the crashing EIP, please?
Well, it oopsed the first time so I rebuilt with debugging on and it didn't die. Not sure what debuggin info will do to the results, but since some of them went up I thought I'd let you see them anyway. I might be out tomorrow so I might not be able to follow up until Monday.
SPECSDET
2.6.0-test5 2.6.0-test5piggin
Threads Ops/sec Ops/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 3232 3248 0.50 16.00 96.96
4 11794 11606 -1.59 -188.00 353.82
16 19008 18723 -1.50 -285.00 570.24
64 18736 17679 -5.64 -1057.00 562.08 *SPECJBB
2.6.0-test5 2.6.0-test5piggin
# of WHs OPs/sec OPs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 10118.42 10100.65 -0.18 -17.77 303.55
4 35316.38 35037.34 -0.79 -279.04 1059.49
7 54126.17 54290.86 0.30 164.69 1623.79
10 56906.64 56703.59 -0.36 -203.05 1707.20
13 51589.86 55509.08 7.60 3919.22 1547.70 *
16 41410.52 51366.41 24.04 9955.89 1242.32 *
19 32944.48 33693.62 2.27 749.14 988.33VOLANOMARK
2.6.0-test5 2.6.0-test5piggin
Msgs/sec Msgs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 40915 42606 4.13 1691.00 1227.45 *
Steve
Quoted 25 lines
Quoted 14 lines · Cliff White
Quoted 14 lines
Nick Piggin wrote:
Con Kolivas wrote:
Hi Con,
Any chance you could give this
http://www.kerneltrap.org/~npiggin/v14/sched-rollup-nopolicy-v14.gz
a try? It should apply against test5.Quoted 6 lines
I have some STP tests scheduled against this also (PLM 2117) Please let me know if you want other combinations tested - am just catching up on
this thread.
cliffw
Quoted 4 lines
Thanks Cliff that would be cool. If you could test this:
http://www.kerneltrap.org/~npiggin/v14/sched-rollup-v14.gz
as well would be good. The previous one is more important though.
sched-rollup-v14 runs good on 2-cpu w/reaim (more in next email):
example:
http://khack.osdl.org/stp/279657/
Has oops on 4-cpu when running the dbt2-1tier database test(below):
Two runs, different oops.
Let me know how much more detail you need.
Both machines are Intel PIII x ~800mhz w/ 1GB RAM/cpu Diffs between the 2 and 4 way would include. :
- different SCSI controllers
- database uses raw IO
kernel .config files should be the same for both, other than SCSI.
cliffw
----------------------------
Sep 10 15:44:30 stp4-000 kernel: sdo: sdo1 Unable to handle kernel paging request at virtual address 4d7a7153 printing eip: c011c1f9 *pde = 0e81a067 *pte = 00000000 Oops: 0002 [#1] CPU: 3 EIP: 0060:[<c011c1f9>] Not tainted EFLAGS: 00010003
EIP is at load_balance+0x2a9/0x4d0
eax: de9c4998 ebx: c366a518 ecx: 4d7a7153 edx: c3672100
esi: c366a518 edi: c366a4f8 ebp: c3e8df64 esp: c3e8df30
ds: 007b es: 007b ss: 0068
Process kernel (pid: 4246, threadinfo=c3e8c000 task=f7b9b300)
Stack: c3669bc0 c366a104 c3669bc0 c366a518 c366a100 00000000 00000003 00000080
0000000f 00000002 c3e8c000 c3671bc0 0000000f c3e8df88 c011c486 c3671bc0
00000000 0000000f 00000000 00000001 00000000 c0412084 c3e8dfc4 c012a6a5
Call Trace:
[<c011c486>] rebalance_tick+0x66/0xa0
[<c012a6a5>] update_process_times+0x45/0x60
[<c0117961>] smp_apic_timer_interrupt+0x141/0x150
[<c010a0ca>] apic_timer_interrupt+0x1a/0x20
Code: 89 19 89 4b 04 8b 47 18 0f ab 42 04 ff 02 89 57 28 8b 5d 08
----------second 4-cpu run, same test
--------
nable to handle kernel paging request at virtual address 20190078
printing eip:c011c9c4
*pde = 00000000
Oops: 0002 [#1] CPU: 1 EIP: 0060:[<c011c9c4>] Not tainted EFLAGS: 00010002
EIP is at schedule+0x224/0x5d0
eax: 00000001 ebx: cacfd940 ecx: 00000001 edx: 20190000
esi: de984460 edi: f73a8e00 ebp: caed3c28 esp: caed3be8
ds: 007b es: 007b ss: 0068
Process awk (pid: 9673, threadinfo=caed2000 task=cacfd940)
Stack: de984460 840e6b72 00000003 d1bf3120 c3661bc0 c3661020 00000001 bfffa000
c11c03e0 00000007 f73a8e00 c3661590 003fe5d0 caed2000 0324ef80 f7983dc0
caed3c34 c011cda6 e8912660 00000001 c0150ed4 c3661034 00000000 00000000
Call Trace:
[<c011cda6>] preempt_schedule+0x36/0x50
[<c0150ed4>] exit_mmap+0x1e4/0x240
[<c011f6a0>] mmput+0x70/0xc0
[<c0169bad>] exec_mmap+0x11d/0x210
[<c0169e03>] flush_old_exec+0x163/0xa10
[<c0169a80>] kernel_read+0x50/0x60
[<c018c2cc>] load_elf_binary+0x2dc/0xbc0
[<c011a148>] pgd_alloc+0x18/0x20
[<c011f59d>] mm_init+0xbd/0x100
[<c0169533>] copy_strings+0x213/0x290
[<c018bff0>] load_elf_binary+0x0/0xbc0
[<c016aa41>] search_binary_handler+0xa1/0x210
[<c016adc4>] do_execve+0x214/0x250
[<c0107c80>] sys_execve+0x50/0x80
[<c0109689>] sysenter_past_esp+0x52/0x71
Code: f0 0f ab 42 78 8b 42 10 05 00 00 00 40 0f 22 d8 8b 8a 9c 00_______________________________________________
cliffw
Quoted 6 lines
-
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/
Quoted 15 lines · Andrew Morton
Quoted 5 lines · Steven Pratt
For specjbb things are looking good from a throughput point of view. ... Volanomark, on the other hand is still off by quite a bit from test4 stock
hmm, thanks.
I'm not sure that volanomark is very representative of any real-world thing.
Quoted 9 lines
Quoted 4 lines
...
If thre is any particular patch/tree combination you would like me to try out, please let me know and I will see if I can get the results for you.Could we please see test5 versus test5 plus Andrew's patch?
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-CAN_MIGRATE_TASK-fix.patch
This patch improves specjjb over test5 and has no real effect on any of kernbench, volanomark or specsdet.
Specjbb Throughput
2.6.0-test5 2.6.0-test5BALANCE
# of WHs OPs/sec OPs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 10118.42 10062.66 -0.55 -55.76 303.55
4 35316.38 34676.03 -1.81 -640.35 1059.49
7 54126.17 52717.84 -2.60 -1408.33 1623.79
10 56906.64 56587.53 -0.56 -319.11 1707.20
13 51589.86 54625.25 5.88 3035.39 1547.70 *
16 41410.52 43120.66 4.13 1710.14 1242.32 *
19 32944.48 35820.89 8.73 2876.41 988.33 *Volanomark
2.6.0-test5 2.6.0-test5BALANCE
Msgs/sec Msgs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 40915 41391 1.16 476.00 1227.45
Quoted 6 lines
and if you have time, also test5 plus sched-CAN_MIGRATE_TASK-fix.patch plus
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-balance-fix-2.6.0-test3-mm3-A0.patch
This patch degrades both specjbb and volanomark, and to a lesser degree specsdet
Specjbb throughput
2.6.0-test5 2.6.0-test5MIGRATE
# of WHs OPs/sec OPs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 10118.42 9980.90 -1.36 -137.52 303.55
4 35316.38 34065.11 -3.54 -1251.27 1059.49 *
7 54126.17 52697.10 -2.64 -1429.07 1623.79
10 56906.64 55466.77 -2.53 -1439.87 1707.20
13 51589.86 43152.57 -16.35 -8437.29 1547.70 *
16 41410.52 45201.21 9.15 3790.69 1242.32 *
19 32944.48 29025.16 -11.90 -3919.32 988.33 *Volanomark
2.6.0-test5 2.6.0-test5MIGRATE
Msgs/sec Msgs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 40915 38518 -5.86 -2397.00 1227.45 *
Quoted 6 lines
What I'm afraid of is that those patches will yield improved results over test5, and that adding
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-2.6.0-test2-mm2-A3.patch
I tried adding this patch to stock test5 and it failed to apply cleanly. I have not had a chance to look at why. Did you mean for this to be applied by itself, or was this supposed to go on top of one of the other patches?
Quoted 3 lines
will slow things down again.
Steve
Quoted 6 lines · Steven Pratt
Quoted 4 lines
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-CAN_MIGRATE_TASK-fix.patch
This patch improves specjjb over test5 and has no real effect on any of kernbench, volanomark or specsdet.
Fine, it's a good fix.
Quoted 8 lines
Quoted 6 lines
and if you have time, also test5 plus sched-CAN_MIGRATE_TASK-fix.patch plus
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-balance-fix-2.6.0-test3-mm3-A0.patch
This patch degrades both specjbb and volanomark, and to a lesser degree specsdet
ok. And just confirming: that was test5 plus
sched-CAN_MIGRATE_TASK-fix.patch plus
sched-balance-fix-2.6.0-test3-mm3-A0.patch?
I didn't expect a regression from sched-balance-fix.
Quoted 9 lines
Quoted 5 lines
What I'm afraid of is that those patches will yield improved results over test5, and that adding
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-2.6.0-test2-mm2-A3.patch
I tried adding this patch to stock test5 and it failed to apply cleanly. I have not had a chance to look at why. Did you mean for this to be applied by itself, or was this supposed to go on top of one of the other patches?
Yes, it applies on top of the other two patches.
Thanks for working on this: it's pretty important right now.
Quoted 21 lines · Andrew Morton
Quoted 7 lines · Steven Pratt
Quoted 4 lines
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-CAN_MIGRATE_TASK-fix.patch
This patch improves specjjb over test5 and has no real effect on any of kernbench, volanomark or specsdet.
Fine, it's a good fix.
Quoted 6 lines
Quoted 6 lines
and if you have time, also test5 plus sched-CAN_MIGRATE_TASK-fix.patch plus
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-balance-fix-2.6.0-test3-mm3-A0.patch
Quoted 9 lines
Quoted 3 lines
This patch degrades both specjbb and volanomark, and to a lesser degree specsdet
ok. And just confirming: that was test5 plus
sched-CAN_MIGRATE_TASK-fix.patch plus
sched-balance-fix-2.6.0-test3-mm3-A0.patch?
No this was test 5 plus sched-CAN_MIGRATE_TASK-fix.patch only. I seems I misread the request. I am running that job now.
Quoted 11 lines
I didn't expect a regression from sched-balance-fix.
Quoted 7 lines
Quoted 7 lines
What I'm afraid of is that those patches will yield improved results over test5, and that adding
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm6/broken-out/sched-2.6.0-test2-mm2-A3.patch
Quoted 8 lines
Quoted 3 lines
I tried adding this patch to stock test5 and it failed to apply cleanly. I have not had a chance to look at why. Did you mean for this to be applied by itself, or was this supposed to go on top of one of the other patches?
Yes, it applies on top of the other two patches.
Thanks for working on this: it's pretty important right now.
Ok, this is submitted as well. Should have results this afternoon.
Steve
Ok, looks like I reversed 2 set of results yesterday when I posted. Here is a more complete (and hopefully accurate) reporting of the 3 patches.
A) *** test5 + sched-CAN_MIGRATE_TASK-fix.patch
degrades volanomark, specjbb and specsdet
B) *** test5 + sched-balance-fix-2.6.0-test3-mm3-A0.patch improves specjbb with no real change on sdet or volanomark
C) *** test5 + sched-CAN_MIGRATE_TASK-fix.patch + sched-balance-fix-2.6.0-test3-mm3-A0.patch degrades volanomark and sdet, more degrade than improvement on specjbb
D) *** test5 + sched-CAN_MIGRATE_TASK-fix.patch + sched-balance-fix-2.6.0-test3-mm3-A0.patch + sched-2.6.0-test2-mm2-A3.patch degrades volanomark and sdet, mixed results on specjbb
Below are the details for each of the runs.
A) *** test5 + sched-CAN_MIGRATE_TASK-fix.patch ********************
Volanomark
2.6.0-test5 2.6.0-test5MIGRATE
Msgs/sec Msgs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 40915 38518 -5.86 -2397.00 1227.45 *
SPECJBB
2.6.0-test5 2.6.0-test5MIGRATE
# of WHs OPs/sec OPs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 10118.42 9980.90 -1.36 -137.52 303.55
4 35316.38 34065.11 -3.54 -1251.27 1059.49 *
7 54126.17 52697.10 -2.64 -1429.07 1623.79
10 56906.64 55466.77 -2.53 -1439.87 1707.20
13 51589.86 43152.57 -16.35 -8437.29 1547.70 *
16 41410.52 45201.21 9.15 3790.69 1242.32 *
19 32944.48 29025.16 -11.90 -3919.32 988.33 * SPECSDET
2.6.0-test5 2.6.0-test5MIGRATE
Threads Ops/sec Ops/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 3232 3111 -3.74 -121.00 96.96 *
4 11794 11383 -3.48 -411.00 353.82 *
16 19008 18726 -1.48 -282.00 570.24
64 18736 18701 -0.19 -35.00 562.08 B) *** test5 + sched-balance-fix-2.6.0-test3-mm3-A0.patch *************************
VOLANOMARK
2.6.0-test5 2.6.0-test5BALANCE
Msgs/sec Msgs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 40915 41391 1.16 476.00 1227.45
SPECJBB
2.6.0-test5 2.6.0-test5BALANCE
# of WHs OPs/sec OPs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 10118.42 10062.66 -0.55 -55.76 303.55
4 35316.38 34676.03 -1.81 -640.35 1059.49
7 54126.17 52717.84 -2.60 -1408.33 1623.79
10 56906.64 56587.53 -0.56 -319.11 1707.20
13 51589.86 54625.25 5.88 3035.39 1547.70 *
16 41410.52 43120.66 4.13 1710.14 1242.32 *
19 32944.48 35820.89 8.73 2876.41 988.33 * SPECSDET
2.6.0-test5 2.6.0-test5BALANCE
# of WHs OPs/sec OPs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 10118.42 10062.66 -0.55 -55.76 303.55
4 35316.38 34676.03 -1.81 -640.35 1059.49
7 54126.17 52717.84 -2.60 -1408.33 1623.79
10 56906.64 56587.53 -0.56 -319.11 1707.20
13 51589.86 54625.25 5.88 3035.39 1547.70 *
16 41410.52 43120.66 4.13 1710.14 1242.32 *
19 32944.48 35820.89 8.73 2876.41 988.33 * C) *** test5 + sched-CAN_MIGRATE_TASK-fix.patch + sched-balance-fix-2.6.0-test3-mm3-A0.patch
VOLANOMARK
2.6.0-test5 2.6.0-test5MIGRATE-BALANCE
Msgs/sec Msgs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 40915 38651 -5.53 -2264.00 1227.45 *
SPECJBB
2.6.0-test5 2.6.0-test5MIGRATE-BALANCE
# of WHs OPs/sec OPs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 10118.42 10103.50 -0.15 -14.92 303.55
4 35316.38 35420.78 0.30 104.40 1059.49
7 54126.17 54256.02 0.24 129.85 1623.79
10 56906.64 57224.95 0.56 318.31 1707.20
13 51589.86 43993.71 -14.72 -7596.15 1547.70 *
16 41410.52 45037.11 8.76 3626.59 1242.32 *
19 32944.48 30018.34 -8.88 -2926.14 988.33 * SPECSDET
2.6.0-test5 2.6.0-test5MIGRATE-BALANCE
Threads Ops/sec Ops/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 3232 3031 -6.22 -201.00 96.96 *
4 11794 11288 -4.29 -506.00 353.82 *
16 19008 18716 -1.54 -292.00 570.24
64 18736 18775 0.21 39.00 562.08 D) *** test5 + sched-CAN_MIGRATE_TASK-fix.patch + sched-balance-fix-2.6.0-test3-mm3-A0.patch +
sched-2.6.0-test2-mm2-A3.patch
VOLANOMARK
2.6.0-test5 2.6.0-test5ALL
Msgs/sec Msgs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 40915 37204 -9.07 -3711.00 1227.45 *
SPECJBB
2.6.0-test5 2.6.0-test5ALL
# of WHs OPs/sec OPs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 10118.42 10124.52 0.06 6.10 303.55
4 35316.38 34240.71 -3.05 -1075.67 1059.49 *
7 54126.17 54015.28 -0.20 -110.89 1623.79
10 56906.64 56618.95 -0.51 -287.69 1707.20
13 51589.86 47911.50 -7.13 -3678.36 1547.70 *
16 41410.52 46771.18 12.95 5360.66 1242.32 *
19 32944.48 33306.14 1.10 361.66 988.33 SPECSDET
2.6.0-test5 2.6.0-test5ALL
Threads Ops/sec Ops/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 3232 3097 -4.18 -135.00 96.96 *
4 11794 11251 -4.60 -543.00 353.82 *
16 19008 18657 -1.85 -351.00 570.24
64 18736 18703 -0.18 -33.00 562.08 Steve