Re: [ck] Re: Linus 2.6.23-rc1
On Fri, 2007-07-27 at 19:35 -0700, Linus Torvalds wrote: > As a long-term maintainer, trust me, I know what matters. And a person who > can actually be bothered to follow up on problem reports is a *hell* of a > lot more important than one who just argues with reporters. > > Linus Once again linus blows a nut getting off about this and that. The fact of the matter linus is a one sided. The fact is linus says what he wants and people think he is god. The fact is noone get code in unless they are a major player in a linux distro. Ingo had much advantage by using fedora users. The fact Con did not take all bugs serious yes that is a player of the game but linus is GOD so all bow before him before he blows his back out while jacking off to his rants about how the kernel and other projects should run. Jory - 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: [ck] Re: Linus 2.6.23-rc1
On Fri, 2007-07-27 at 19:35 -0700, Linus Torvalds wrote: As a long-term maintainer, trust me, I know what matters. And a person who can actually be bothered to follow up on problem reports is a *hell* of a lot more important than one who just argues with reporters. Linus Once again linus blows a nut getting off about this and that. The fact of the matter linus is a one sided. The fact is linus says what he wants and people think he is god. The fact is noone get code in unless they are a major player in a linux distro. Ingo had much advantage by using fedora users. The fact Con did not take all bugs serious yes that is a player of the game but linus is GOD so all bow before him before he blows his back out while jacking off to his rants about how the kernel and other projects should run. Jory - 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: [ck] Re: swap-prefetch: 2.6.22 -mm merge plans
Con Kolivas wrote: > Here's a better swap prefetch tester. Instructions in file. > > Machine with 2GB ram and 2GB swapfile > > Prefetch disabled: > ./sp_tester > Ram 2060352000 Swap 197342 > Total ram to be malloced: 3047062000 bytes > Starting first malloc of 1523531000 bytes > Starting 1st read of first malloc > Touching this much ram takes 809 milliseconds > Starting second malloc of 1523531000 bytes > Completed second malloc and free > Sleeping for 600 seconds > Important part - starting reread of first malloc > Completed read of first malloc > Timed portion 53397 milliseconds > > Enabled: > ./sp_tester > Ram 2060352000 Swap 197342 > Total ram to be malloced: 3047062000 bytes > Starting first malloc of 1523531000 bytes > Starting 1st read of first malloc > Touching this much ram takes 676 milliseconds > Starting second malloc of 1523531000 bytes > Completed second malloc and free > Sleeping for 600 seconds > Important part - starting reread of first malloc > Completed read of first malloc > Timed portion 26351 milliseconds > echo 1 > /proc/sys/vm/overcommit_memory swapoff -a swapon -a ./sp_tester Ram 1153644000 Swap 1004052000 Total ram to be malloced: 165567 bytes Starting first malloc of 827835000 bytes Starting 1st read of first malloc Touching this much ram takes 937 milliseconds Starting second malloc of 827835000 bytes Completed second malloc and free Sleeping for 600 seconds Important part - starting reread of first malloc Completed read of first malloc Timed portion 15011 milliseconds echo 0 > /proc/sys/vm/overcommit_memory swapoff -a swapon -a ./sp_tester Ram 1153644000 Swap 1004052000 Total ram to be malloced: 165567 bytes Starting first malloc of 827835000 bytes Starting 1st read of first malloc Touching this much ram takes 1125 milliseconds Starting second malloc of 827835000 bytes Completed second malloc and free Sleeping for 600 seconds Important part - starting reread of first malloc Completed read of first malloc Timed portion 14611 milliseconds - 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: [ck] Re: swap-prefetch: 2.6.22 -mm merge plans
Con Kolivas wrote: Here's a better swap prefetch tester. Instructions in file. Machine with 2GB ram and 2GB swapfile Prefetch disabled: ./sp_tester Ram 2060352000 Swap 197342 Total ram to be malloced: 3047062000 bytes Starting first malloc of 1523531000 bytes Starting 1st read of first malloc Touching this much ram takes 809 milliseconds Starting second malloc of 1523531000 bytes Completed second malloc and free Sleeping for 600 seconds Important part - starting reread of first malloc Completed read of first malloc Timed portion 53397 milliseconds Enabled: ./sp_tester Ram 2060352000 Swap 197342 Total ram to be malloced: 3047062000 bytes Starting first malloc of 1523531000 bytes Starting 1st read of first malloc Touching this much ram takes 676 milliseconds Starting second malloc of 1523531000 bytes Completed second malloc and free Sleeping for 600 seconds Important part - starting reread of first malloc Completed read of first malloc Timed portion 26351 milliseconds echo 1 /proc/sys/vm/overcommit_memory swapoff -a swapon -a ./sp_tester Ram 1153644000 Swap 1004052000 Total ram to be malloced: 165567 bytes Starting first malloc of 827835000 bytes Starting 1st read of first malloc Touching this much ram takes 937 milliseconds Starting second malloc of 827835000 bytes Completed second malloc and free Sleeping for 600 seconds Important part - starting reread of first malloc Completed read of first malloc Timed portion 15011 milliseconds echo 0 /proc/sys/vm/overcommit_memory swapoff -a swapon -a ./sp_tester Ram 1153644000 Swap 1004052000 Total ram to be malloced: 165567 bytes Starting first malloc of 827835000 bytes Starting 1st read of first malloc Touching this much ram takes 1125 milliseconds Starting second malloc of 827835000 bytes Completed second malloc and free Sleeping for 600 seconds Important part - starting reread of first malloc Completed read of first malloc Timed portion 14611 milliseconds - 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/
