Skip to contentSkip to conversation

Wonderful World of Linux 2.6 - Final

DISCUSSION Joe Pranevich 3 participants 6 messages Dec 18, 2003 – Dec 19, 2003

lore
Share & tools
lore
#0 lore raw

Hello,

I haven't even seen the email yet from linux-kernel about the v2.6 release, but if Slashdot says it's so, it *must* be true. I have just put the finishing touches on my document describing many of the changes in the new kernel release. If you're interested, please check it out. It should be pretty accurate.

Check it out:

HTML - http://kniggit.net/wwol26.html
TEXT - http://kniggit.net/wwol26.txt

Happy Holidays,

Joe

#1 lore raw
Quoted 8 lines · Joe Pranevich

Hello,

I haven't even seen the email yet from linux-kernel about the v2.6 release, but if Slashdot says it's so, it *must* be true. I have just put the finishing touches on my document describing many of the changes in the new kernel release. If you're interested, please check it out. It should be pretty accurate.

Quoted 4 lines

Check it out:

HTML - http://kniggit.net/wwol26.html
TEXT - http://kniggit.net/wwol26.txt

Hyperthreading:

"...that the scheduler now knows how to recognize and optimize processor loads across both real and virtual processors within a machine."

This is not true. Ingo's shared runqueue patch did not make it into 2.6, nor did Nick's scheduler domain patch. Workloads with low loads and HT will not be scheduled optimally, for example, a kernel compile with -j4 on a 4-way P4, with and without HT:

average of 10 kernel compiles with -j4 on 2.6.0-test9:

HT disabled: Elapsed: 145.086s User: 513.808s System: 44.724s CPU: 384.5% HT enabled: Elapsed: 172.463s User: 633.856s System: 48.003s CPU: 394.8%

-Andrew Theurer

#2 lore raw
Quoted 9 lines · Andrew Theurer
Quoted 8 lines · Joe Pranevich

Hello,

I haven't even seen the email yet from linux-kernel about the v2.6 release, but if Slashdot says it's so, it *must* be true. I have just put the finishing touches on my document describing many of the changes in the new kernel release. If you're interested, please check it out. It should be pretty accurate.

Quoted 6 lines
Quoted 4 lines

Check it out:

HTML - http://kniggit.net/wwol26.html
TEXT - http://kniggit.net/wwol26.txt

Hyperthreading:

Damn, I should really read all the emails first... I'll blame it on the email client, yeah, that's it :)

Anyway, looks like Nick already caught this, so I guess consider the benchmark results in the previous email as proof...

#3 lore raw
In reply to Andrew Theurer
Quoted 7 lines · Andrew Theurer

be scheduled optimally, for example, a kernel compile with -j4 on a 4-way P4, with and without HT:

average of 10 kernel compiles with -j4 on 2.6.0-test9:

HT disabled: Elapsed: 145.086s User: 513.808s System: 44.724s CPU: 384.5% HT enabled: Elapsed: 172.463s User: 633.856s System: 48.003s CPU: 394.8%

is that 4-way a 4-logical-way or 4-physical-way? If it's a 4-logical way, this workload is much closer to the best case than the worst case. I'm guessing a simple -j2 or -j3 should do much worse than that.

#4 lore raw
Quoted 4 lines · Andrea Arcangeli
Quoted 3 lines · Andrew Theurer

be scheduled optimally, for example, a kernel compile with -j4 on a 4-way P4, with and without HT:

Quoted 8 lines
Quoted 4 lines

average of 10 kernel compiles with -j4 on 2.6.0-test9:

HT disabled: Elapsed: 145.086s User: 513.808s System: 44.724s CPU: 384.5% HT enabled: Elapsed: 172.463s User: 633.856s System: 48.003s CPU: 394.8%

is that 4-way a 4-logical-way or 4-physical-way? If it's a 4-logical way, this workload is much closer to the best case than the worst case. I'm guessing a simple -j2 or -j3 should do much worse than that.

This is 4-way physical/4-way logical (no HT) vs 4-way physical/8-way logical (with HT)

#5 lore raw
Quoted 10 lines · Andrew Theurer
Quoted 9 lines · Andrea Arcangeli
Quoted 7 lines · Andrew Theurer

be scheduled optimally, for example, a kernel compile with -j4 on a 4-way P4, with and without HT:

average of 10 kernel compiles with -j4 on 2.6.0-test9:

HT disabled: Elapsed: 145.086s User: 513.808s System: 44.724s CPU: 384.5% HT enabled: Elapsed: 172.463s User: 633.856s System: 48.003s CPU: 394.8%

Quoted 6 lines
Quoted 3 lines

is that 4-way a 4-logical-way or 4-physical-way? If it's a 4-logical way, this workload is much closer to the best case than the worst case. I'm guessing a simple -j2 or -j3 should do much worse than that.

This is 4-way physical/4-way logical (no HT) vs 4-way physical/8-way logical (with HT)

ok then it was closer to the worst case ;)