Posted by
michael
on from the make-kpkg-kernel_image dept.
Sivar writes "Andrew Morton of EXT3 fame has posted benchmarks of Linux 2.5.47 prerelease compared with the latest from the current 2.4 series. With some tasks more than tripling in performance, the future looks very promising."
Re:Can't get a speedup of more than 10
by
Zorton
·
· Score: 3, Insightful
So in other words the more time you spend rescheduling things the less time you have for executing the code you have scheduled.
Hmm..... sounds like modern business management:)
Re:Nice to see Linux "Growing Up"
by
iabervon
·
· Score: 3, Insightful
IBM is also going to stay in the high-end hardware department; it'll be "Sure commodity hardware is great for the workstation, but what about your 8 TB database that has to survive even if someone saws it in half down the middle?" This also puts them in, essentially, the BIOS department for these machines (you want to run you web site off of whatever portion of your database machine isn't actually being used by the database, without risking problems if the web server gets hacked).
Karma whore or just trolling?
by
Dante
·
· Score: 3, Insightful
If I pulled a gif compleatly out of context as proof of anything would you trust me?
-- "think of it as evolution in action"
Re:Make it simple please
by
momobaxter
·
· Score: 3, Insightful
A home user (meaning non hacker) never has the need to recompile a kernel. NEVER. Your distribution has all the modules available and if you're running the more popular distros, they will even detect your hardware and load the module for you.
Sometimes people shouldn't mess with stuff, the kernel is one of those things. RedHat does a good job with their builds and an average user doesn't need to rebuilt it at all. A more experienced user might want to tweak, but then he can use make menuconfig or make config...and choose his options.
My grandmother will never recompile her kernel.
-- "Full sources for linux currently runs to about 200kB compressed" --Linus Torvalds 31-Jan-1992
> would be to tag certain processes so that they > will never be moved into swap for disk buffers
I beleive that this is what the sticky bit was intended for. Before I go about explaining what it is and how to use it, does anyone know if Linux actually *honors* the sticky bit or does it just have it for compatibility?
Slashdot Mirror
So in other words the more time you spend rescheduling things the less time you have for executing the code you have scheduled.
:)
Hmm..... sounds like modern business management
IBM is also going to stay in the high-end hardware department; it'll be "Sure commodity hardware is great for the workstation, but what about your 8 TB database that has to survive even if someone saws it in half down the middle?" This also puts them in, essentially, the BIOS department for these machines (you want to run you web site off of whatever portion of your database machine isn't actually being used by the database, without risking problems if the web server gets hacked).
If I pulled a gif compleatly out of context as proof of anything would you trust me?
"think of it as evolution in action"
A home user (meaning non hacker) never has the need to recompile a kernel. NEVER. Your distribution has all the modules available and if you're running the more popular distros, they will even detect your hardware and load the module for you.
Sometimes people shouldn't mess with stuff, the kernel is one of those things. RedHat does a good job with their builds and an average user doesn't need to rebuilt it at all. A more experienced user might want to tweak, but then he can use make menuconfig or make config...and choose his options.
My grandmother will never recompile her kernel.
"Full sources for linux currently runs to about 200kB compressed" --Linus Torvalds 31-Jan-1992
> would be to tag certain processes so that they
> will never be moved into swap for disk buffers
I beleive that this is what the sticky bit was intended for. Before I go about explaining what it is and how to use it, does anyone know if Linux actually *honors* the sticky bit or does it just have it for compatibility?