Re: Scaling noise

Larry McVoy
2003-09-10T15:13:15Z

On Wed, Sep 10, 2003 at 11:02:34AM -0400, Timothy Miller wrote:
> Larry McVoy wrote:
> >You don't make that much money, if any, on the high end, the R&D costs
> >dominate. But you make money because people buy the middle of the road
> >because you have the high end. If you don't, they feel uneasy that they
> >can't grow with you. The high end enables the sales of the real money
> >makers. It's pure marketing, the high end could be imaginary and as
> >long as you convinced the customers you had it you'd be more profitable.
>
> I think some time in the 90's, Chevy considered discontinuing the
> Corvette. Then they realized that that would kill their business.
> People who would never buy a Corvette buy other GM cars just because the
> Corvette exists. Lots of reasons: It's an icon that people recognize,
> it makes them feel that other Chevys will share some of the Corvette
> quality, etc.

Yeah, yeah. I get that. What people here are not getting is that if you
are building the low end cars out of the same parts as the high end cars
then you are driving up the cost of your low end cars. Same thing for
the OS. The point is to have some answer that lets people go "ohhh,
wow, that's a big fast OS, now, isn't it?" without having screwed up
the low end and/or having made the source base a rats nest.

Dave and friends can protest as much as they want that the kernel works
and it scales (it does work, it doesn't scale by comparison to something
like IRIX) but that's missing the point. They refused to answer the
question about listing the locks in the I/O path. In a uniprocessor
OS any idiot can tell you the locks in the I/O path. They didn't even
try to list them, they can't do it now. What's it going to be like
when the system scales 10x more?

I've been through this. These guys are kidding themselves and by the
time they wake up there is too much invested in the source base to
unravel the mess.

What people keep missing, over and over, is that I'm perfectly OK with
the idea of making the system work on a big box. I've made a proposal
for a way that I see has far less pressure on it to screw up the OS.
You don't have to scale the I/O path when you can throw a kernel at every
device if you want. The I/O path is free, it's uniprocessor, simple.
Think about it. We're all trying to have the bragging rights, I do
enough sales that I understand the importance of those. It just makes
me sick to think that we could get them far faster and far more easily
than the commercial Unix guys did and than Microsoft will and instead
we're playing by the wrong rules.

Don't like my rules? Make up some different ones. But doing the same
old thing is just bloody stupid.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm