|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Tech News Breaking and important technical news developments |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
||||
|
Quote:
__________________
My site: http://microchip.bplaced.net My repo: http://download.opensuse.org/repositories/home:/microchip8 SUSE Unbound Forum: http://suseunbound.lefora.com Do coders dream of sheep() ? |
|
||||
|
Linus calls Linux 'bloated and huge' • The Register
Quote:
|
|
|||
|
Hmm, interesting as the comments are, I wonder how significant this is, if one considers the whole linux distribution?
As users upgrade hardware to accomodate yearly decreases in performance, due to more function in applications, and improving multimedia quality, will they notice that 2% per annum? I can understand why Intel would like to know how and why the linux kernel is feeding the takeup of improving, and presumably more profitable, processor technolgy.
|
|
||||
|
No wonder the kernel is getting bloated when you constantly add new drivers and such. Linus is looking from code-side point of view and of course that's bloated with so many things in it, especially drivers and file systems. However looking from another point of view, a custom-configured and compiled kernel, it can be made pretty small with only the absolute minimum one would need.
As for the kernel getting slows, I've experienced the exact opposite here on my desktops, especially on the interactivity side which is part of performance measures. Comparing older kernels with the old O(1) scheduler against the new CFS O(log N) scheduler, I find my apps to be much snappier and starting faster too
__________________
My site: http://microchip.bplaced.net My repo: http://download.opensuse.org/repositories/home:/microchip8 SUSE Unbound Forum: http://suseunbound.lefora.com Do coders dream of sheep() ? |
|
||||
|
Bloat is bound to happen no matter what OS you use, as more features are added the bigger the bigger the bloat.
|
|
||||
|
It is inevitable for a monolithic kernel, which is what Linux, Windows, and Unix is. I did research on monolithic kernels vs microkernels. I found from my research that both designs have their share of problems. Monolithic kernels have problems with size, maintainability, and sometimes stability, but they do well on performance. Microkernels are very small, but they suffer from performance problems due to overhead imposed by numerous external calls for basic system functions such as drivers and file systems.
I think the best design would be a hybrid approach. It may be better for Linux in the long run to remove from the kernel (into external components) what can be removed without consequence. I think Linux is kind of working in that direction anyway with dynamically loadable/unloadable modules. |
|
||||
|
Hint: Windows is hybrid and so is OS X
__________________
My site: http://microchip.bplaced.net My repo: http://download.opensuse.org/repositories/home:/microchip8 SUSE Unbound Forum: http://suseunbound.lefora.com Do coders dream of sheep() ? |
|
|||
|
Quote:
|
![]() |
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|