Skip to contentSkip to conversation

Syslets, "Threadlets", generic AIO support, v3

PATCH Al Boldi 3 participants 3 messages Feb 27, 2007 – Mar 1, 2007

lore
Share & tools
lore

Al Boldi

author
#0 lore raw
Quoted 9 lines · Theodore Tso
Quoted 3 lines · Evgeniy Polyakov

Obviously there are bugs, it is simply how things work. And debugging state machine code has exactly the same complexity as debugging multi-threading code - if not less...

Evgeniy,

I think what you are not hearing, and what everyone else is saying (INCLUDING Linus),

Excluding possibly many others.

Quoted 3 lines

is that for most programmers, state machines are much, much harder to program, understand, and debug compared to multi-threaded code.

That's why you introduce an infrastructure that hides all the nitty-gritty plumbing, and makes it easy to use.

Quoted 4 lines

You may disagree (were you a MacOS 9 programmer
in another life?), and it may not even be true for you if you happen to be one of those folks more at home with Scheme continuations, for example.

Personal attacks are really rather unhelpful/unscientific.

Quoted 4 lines

But it is true that for most kernel programmers, threaded programming is much easier to understand, and we need to engineer the kernel for what will be maintainable for the majority of the kernel development community.

What's probably true is that, for a kernel to stay competitive you need two distinct traits:

1. Stability
2. Performance

And you can't get that, by arguing that the kernel development community doesn't have the brains to code for performance, which I dearly doubt.

So, instead of using intimidating language to force one's opinion thru, especially when it comes from those in control, why not have a democratic vote?

Thanks!

--
Al

#1 lore raw
Quoted 6 lines · Al Boldi
Quoted 4 lines

You may disagree (were you a MacOS 9 programmer
in another life?), and it may not even be true for you if you happen to be one of those folks more at home with Scheme continuations, for example.

Personal attacks are really rather unhelpful/unscientific.

Just to be clear; this wasn't a personal attack. I know a lot of people who I greatly respect who were MacOS and Scheme programmers (I went to school at MIT, after all, the birthplace of Scheme). The reality though is that most people don't program that way, and their brains aren't wired in that fashion. There is a reason why procedural languages are far more common than purely functional models, and why aside from (pre-version 10) MacOS, most OS's don't use an event driven system call interface.

Quoted 3 lines

So, instead of using intimidating language to force one's opinion thru, especially when it comes from those in control, why not have a democratic vote?

So far, I'd have to say the people arguing for an event driven model are in the distinct minority...

And as far as voting is concerned, I prefer informed voters who can explain why, in their own words, why they are in favor of a particular alternative.

Regards,

- Ted

#2 lore raw
In reply to Al Boldi

Hi!

Quoted 11 lines
Quoted 4 lines

But it is true that for most kernel programmers, threaded programming is much easier to understand, and we need to engineer the kernel for what will be maintainable for the majority of the kernel development community.

What's probably true is that, for a kernel to stay competitive you need two distinct traits:

1. Stability
2. Performance

Quoted 6 lines

And you can't get that, by arguing that the kernel development community doesn't have the brains to code for performance, which I dearly doubt.

So, instead of using intimidating language to force one's opinion thru, especially when it comes from those in control, why not have a democratic vote?

Linus cast his vote, and as that is only vote that matters, can we end this discussion? (Eugeny is not willing to listen to Linus, but I guess that's Eugeny's problem at this point).
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html