Linus: Linux 'Bloated and Huge', Development Process Working
Linked by Thom Holwerda on Tue 22nd Sep 2009 15:34 UTC, submitted by google_ninja
Linux During the roundtable discussion at LinuxCon this year, Linus Torvalds made some pretty harsh remarks about the current state of the Linux kernel, calling it "huge and bloated", and that there is no plan in sight to solve the problem. At the same time, he also explained that he is very happy with the current development process of the kernel, and that his job has become much easier.
E-mail Print r 7   · Read More · 84 Comment(s) http://osne.ws/h4v
Thread beginning with comment 385491
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: performance
by broch on Tue 22nd Sep 2009 17:45 UTC in reply to "RE: performance"
broch
Member since:
2006-05-04

this (size and functionality) has nothing to do with the performance problem.

1) Apply wherever possible specialty tools:
CPU scheduler is a good example what options are there
CFS performance degraded seriously in time. It is big trying to me "smart"(er than..) and at the end we get crippled performance.
Now there is BFS, small and efficient for desktop use only.
Why not to have two schedulers

Trying to do everything is wors idea ever, get one cpu scheduler for servers another for desktop. Nowadays kernel is trying to be jack of all trades with mediocre results.

2) code reuse would also help (including size)

Reply Parent Score: 1

RE[3]: performance
by siride on Tue 22nd Sep 2009 18:13 in reply to "RE[2]: performance"
siride Member since:
2006-01-02

Somehow I very much doubt the scheduler is the problem with desktop performance. X performance and application efficiency probably play a much bigger role.

Reply Parent Score: 2

RE[4]: performance
by broch on Tue 22nd Sep 2009 18:26 in reply to "RE[3]: performance"
broch Member since:
2006-05-04

scheduler was only an example. I don't think that scheduler only is responsible for the problem.
Kernel is trying to please all possible users, desktop server and so on. This does not work very well.

and yes, it (cpu scheduler) does have a lot to do with (also desktop) performance. If you would check recent lkml discussions, you would clearly see that.

Reply Parent Score: 1