Skip to contentSkip to conversation

Driver Model 2 Proposal - Linux Kernel Performance v Usability

DISCUSSION James Clark 19 participants 33 messages Sep 4, 2003 – Sep 15, 2003 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 1062637356.846.3471.camel@cube

#1 lore raw

Thank you for this (and the few other) sensible appraisal of my 'proposal'.

I'm very surprised by the number of posts that have ranted about Open/Close source, GPL/taint issues etc. This is not about source code it is about making Linux usable by the masses. It may be technically superior to follow the current model, but if the barrier to entry is very high (and it is!) then the project will continue to be a niche project. A binary model doesn't alter the community or the benefits of public source code. I agree that it is an extra interface and will carry a performance hit - I think this is worth it. Windows has many faults but drivers are often compatible across major releases and VERY compatible across minor releases. It is no accident that it has 90% of the desktop market. If we are going to improve this situation this issue MUST be confronted.

I am currently collating the arguments for and (mostly) against the idea. If I don't get flamed in the meantime I may come back with more...

James

Quoted 124 lines · you
Quoted 2 lines

Following my initial post yesterday please find attached my proposal for a binary 'plugin' interface:

There was one, called UDI. It was rejected.

Quoted 3 lines

I believe that sometimes the ultimate goals of stability and portability get lost in the debate on OSS and desire to allow anyone to contribute.

If "stability" means "no changes", then don't upgrade for a few years.

If "stability" means "no crashes", then a binary interface is harmful. Extra layers mean extra bugs, and the layers make debugging more difficult.

Portability??? Linux beats every other OS for that.

Quoted 5 lines

3. Design 'plugin' interface to be extensible as possible and then rarely remove support from interface. Extending interface is fine but should be done in a considered way to avoid interface bloat. Suggest interface supports dependant 'plugins'

Removal of crud is important. We keep things simple, fast, and small.

Quoted 2 lines

4. Allow 'plugins' to be bypassed at boot - perhaps a minimal 'known good' list

This works already. Put "init=/bin/bash" on the kernel command line (at the lilo, grub, or syslinux prompt) and you will bypass all of the start-up scripts. That will cause you to skip any modules (drivers, plugins, whatever) that would be loaded by your boot scripts.

Quoted 2 lines

5. Ultimately, even FS 'plugins' could be created although IPL would be required to load these.

IPL is some old IBM mainframe term. In the Linux and UNIX world we call it boot, bootstrap, start-up, etc.

We can already make our filesystem a loadable module. Your boot loader (lilo, grub, or syslinux) has the ability to load an "initrd". This gives you something kind of like a ramdisk, but without the wasted space. The scripts on the initrd can then load drivers for your disk (IDE, SCSI, etc.) and filesystem (ext2, ext3, reiserfs, reiser4, jfs, xfs, etc.). After the drivers are loaded, there's a mount() syscall, a pivit_root() syscall... and soon enough the initrd is gone and you have the real root filesystem mounted.

Quoted 1 line

1. Make Linux easier to use

I doubt it. There would be a promise of binary compatibility that wouldn't be possible to maintain. Microsoft fails often enough; notice how Win98 broke SCSI drivers that people were using.

Without such a promise, people don't grow to depend on an interface that ultimately can't be supported.

Quoted 2 lines

2. The ability to replace even very core Kernel components without a restart.

That's a fantasy, more-or-less. Binary patches can be done on a case-by-case basis at great expense. Novell did it sometimes. Microsoft didn't even try.

Quoted 2 lines

3. Allow faulty 'plugins' to be fixed/replaced in isolation. No other system impact.

Linux supports this as well as can be. Any driver (module, plugin, whatever) has the ability to crash your system BY DEFINITION of having the necessary power to control your hardware.

Quoted 2 lines

4. 'Plugins' could create their own interfaces as load time. This would remove the need to pre-populate /dev.

We have this as an option; we call it devfs. It has a problem: permission changes will not persist across a reboot.

Quoted 1 line

5. Remove need for joe soap user to often recompile Kernel.

Already done: buy a CD-ROM from Red Hat

Quoted 2 lines

6. Remove link between specific module versions and Kernel versions.

It's partly done (optional), and partly not desireable.

Quoted 4 lines

7. Reduce need for major Kernel releases. Allow effort to concentrate on improving Kernel not maintaining ever increasing Kernel source that includes support for the 'Kitchen Sink'

No. It's damn nice to have all the source code in one place, all updated together, supporting whatever old hardware one may have.

It's only recently (2.5.xx kernel series) that Linux dropped support for the PC-XT hard drive interface. Know what that is? It was introduced around 1981 maybe. Support was only dropped because all the disks have died.

Quoted 4 lines

8. Make core Kernel more stable. Less releases and less changes mean less bugs. It would be easy to identify offending 'plugin' by simply starting up the Kernel with it disabled.

We can do this now. It's not a kernel issue though. Starting up with things disabled is a feature of your boot scripts, which are provided by your Linux distribution. See your Red Hat documentation, or your SuSE documentation, etc.

Quoted 3 lines

9. Remove need for modules to be maintained in sync with each Kernel thus freeing 'module' developers to add improved features or work on new projects.

Then nobody would maintain them.

#2 lore raw
Quoted 9 lines · James Clark

Thank you for this (and the few other) sensible appraisal of my 'proposal'.

I'm very surprised by the number of posts that have ranted about Open/Close source, GPL/taint issues etc. This is not about source code it is about making Linux usable by the masses. It may be technically superior to follow the current model, but if the barrier to entry is very high (and it is!) then the project will continue to be a niche project. A binary model doesn't alter the community or the benefits of public source code. I agree that it is an extra interface and will carry a performance hit - I think this is worth it.

The thing is, most Linux developers (and I'm sure it's above 51% or maybe they're just louder?) want drivers to be GPL compatible open source. Having a static binary driver interface just doesn't mix very well for that. And as things happen (and how it should be), in a well kept stable series, the binary interfaces won't change that much. But it will change for different options, like SMP, preempt, numa, etc.

Quoted 4 lines

Windows has many faults but drivers are often compatible across major releases and VERY compatible across minor releases. It is no accident that it has 90% of the desktop market. If we are going to improve this situation this issue MUST be confronted.

Have you ever seen the source code available for a windows driver? Windows doesn't let you customize the kernel. You just get what they give you. With the customization possible in Linux you get many advantages, and the disadvantage that the binary interface can change depending on the compile options.

#3 lore raw

I agree that at first sight the two concepts (Binary 'plugins' and GPL) don't mix well but this is actually FUD which obscures the issue of making the kernel much easier to deal with for the masses. Like it or not, 99+% of 'potential users' don't want/need to recompile their whole kernel, with the risks that it has, to add one minor feature.

James

Quoted 35 lines · Mike Fedyk
Quoted 11 lines · James Clark

Thank you for this (and the few other) sensible appraisal of my 'proposal'.

I'm very surprised by the number of posts that have ranted about Open/Close source, GPL/taint issues etc. This is not about source code it is about making Linux usable by the masses. It may be technically superior to follow the current model, but if the barrier to entry is very high (and it is!) then the project will continue to be a niche project. A binary model doesn't alter the community or the benefits of public source code. I agree that it is an extra interface and will carry a performance hit - I think this is worth it.

The thing is, most Linux developers (and I'm sure it's above 51% or maybe they're just louder?) want drivers to be GPL compatible open source. Having a static binary driver interface just doesn't mix very well for that. And as things happen (and how it should be), in a well kept stable series, the binary interfaces won't change that much. But it will change for different options, like SMP, preempt, numa, etc.

Quoted 4 lines

Windows has many faults but drivers are often compatible across major releases and VERY compatible across minor releases. It is no accident that it has 90% of the desktop market. If we are going to improve this situation this issue MUST be confronted.

Have you ever seen the source code available for a windows driver? Windows doesn't let you customize the kernel. You just get what they give you. With the customization possible in Linux you get many advantages, and the disadvantage that the binary interface can change depending on the compile options.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#4 lore raw
Quoted 3 lines · James Clark

I agree that at first sight the two concepts (Binary 'plugins' and GPL) don't mix well but this is actually FUD which obscures the issue of making the kernel much easier to deal with for the masses.

There is some point in easing the use of external modules with a binary interface. Case in point, winmodems & nvidia. But the question is if we really want to encourage binary-only modules, which most in the community don't.

In Linux, drivers are kernel modules, and that has the ability to completly hose the rest of the kernel if there are bugs in the module. You won't get around this with a static binary interface unless you put a lot of overhead and layering between a module and the kernel. Right now, once a module is loaded, it IS now part of the kernel.

Quoted 3 lines

Like it or not, 99+% of
'potential users' don't want/need to recompile their whole kernel, with the risks that it has, to add one minor feature.

And they don't. If they don't know how, or don't want to, they should be using a distribution kernel that does it for them.

Are you saying that you want to add or change something now that is not modularized yet?

If so what and how? Yes you can say with this nice binary interface you can add whatever feature you want with a nice new driver. Well, you can do that now. All you have to do is compile against the source of the kernel you're running, and you can insert it into the kernel without rebooting.

And if you're trying to change something in a running kernel that isn't a module you can unload (so the root filesystem is out at the very least), then you're talking about an entirely new can of worms.

#5 lore raw
In reply to James Clark
Quoted 5 lines · James Clark

I agree that at first sight the two concepts (Binary 'plugins' and GPL) don't mix well but this is actually FUD which obscures the issue of making the kernel much easier to deal with for the masses. Like it or not, 99+% of 'potential users' don't want/need to recompile their whole kernel, with the risks that it has, to add one minor feature.

Those 99+% are going to use a distro. A popular Linux distro is a rough equivalent of a Windows install disk in terms of ease of use, feature set and intended audience.
Distro can handle this problem (of driver ABI or absence thereof) in any way it wants. I can imagine it can even go to the great pains and introduce binary driver ABI. But unlikely.

OTOH I believe core kernel folks will not accept your proposal. Stay a bit longer on lkml and you will understand why. --
vda

#6 lore raw
In reply to Mike Fedyk

From: "Mike Fedyk" <[email protected]>

Quoted 1 line

Have you ever seen the source code available for a windows driver?

Windows

Quoted 4 lines

doesn't let you customize the kernel. You just get what they give you. With the customization possible in Linux you get many advantages, and the disadvantage that the binary interface can change depending on the compile options.

As a matter of fact, yes. Their (expensive) developer kits have SOME examples. Of course, much of the information you need for any sort of driver that is just a weensie bit strange is completely missing. It makes a specialized USB serial port to MIDI driver very difficult to build and even worse to deploy neatly without a lot of user interaction.

{^_^}

#7 lore raw
In reply to James Clark
Quoted 3 lines · James Clark

I'm very surprised by the number of posts that have ranted about Open/Close source, GPL/taint issues etc. This is not about source code it is about making Linux usable by the masses.

How would "making it easier to include impossible to debug device drivers" help towards your goal of making Linux more usable ?

Signature · 3 lines
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
#8 lore raw

Why would binary drivers be any harder to debug than the existing binary kernel. If you want to debug something use the source code. My proposal doesn't remove the need for quality public source code but it does isolate the kernel components and allow for 'plugin' use on different kernels both old and new.

If a relatively small kernel component can be turned on/off and upgraded at will, without changing ANYTHING else, this would be a big step forward.

James

Quoted 8 lines · you
Quoted 3 lines · James Clark

I'm very surprised by the number of posts that have ranted about Open/Close source, GPL/taint issues etc. This is not about source code it is about making Linux usable by the masses.

How would "making it easier to include impossible to debug device drivers" help towards your goal of making Linux more usable ?

#9 lore raw

Heh. You want stable plugin API.

It will always end as bloat:

(a) you add plugin API
(b) its not sufficient, so you add revision 1 of the API
(you still have to support rev 0 because some plugins are binary-only)
(c) its not sufficient, so you add revision 2 of the API
(now you have 3 versions of API to maintain)
...

Alternatively you can start with over-designed API from the beginning :-).

--bartlomiej

Quoted 20 lines · James Clark

Why would binary drivers be any harder to debug than the existing binary kernel. If you want to debug something use the source code. My proposal doesn't remove the need for quality public source code but it does isolate the kernel components and allow for 'plugin' use on different kernels both old and new.

If a relatively small kernel component can be turned on/off and upgraded at will, without changing ANYTHING else, this would be a big step forward.

James

Quoted 8 lines · you
Quoted 3 lines · James Clark

I'm very surprised by the number of posts that have ranted about Open/Close source, GPL/taint issues etc. This is not about source code it is about making Linux usable by the masses.

How would "making it easier to include impossible to debug device drivers" help towards your goal of making Linux more usable ?

#10 lore raw
In reply to James Clark
Quoted 2 lines · James Clark

If a relatively small kernel component can be turned on/off and upgraded at will, without changing ANYTHING else, this would be a big step forward.

It already can, the install tool just happens to involve invoking gcc and wrapping it nicely. People have already solved that. I'm actually less worried in some ways about the binary only module wrapper question because source wrappers around a binary module to handle glueing them together puts the shipper in conflict with a patent filing owned by a very large hardware company as well as in GPL questionmarks..

#11 lore raw
In reply to James Clark
Quoted 5 lines · James Clark

Why would binary drivers be any harder to debug than the existing binary kernel. If you want to debug something use the source code. My proposal doesn't remove the need for quality public source code but it does isolate the kernel components and allow for 'plugin' use on different kernels both old and new.

Your first statement doesn't make sense.

We don't debug binary kernels by themselves - we debug them with source.

Binary drivers that come without source are almost impossible to debug.

If we can't debug the drivers, we'll soon have a Linux community that's full of broken drivers.

If broken binary-only drivers becomes significant for many users, Linux will become much less fun - and it may harm its adoption and improvment.

Some would say the problem of binary-only drivers is already significantly harming the development process: think of the people running 2.4-only drivers who cannot be involved in 2.6 testing or development.

Also the rate at which new open source drivers are produced will decrease, because there will be less useful source for authors to learn from.

-- Jamie

#12 lore raw
In reply to James Clark
Quoted 14 lines · James Clark

Thank you for this (and the few other) sensible appraisal of my 'proposal'.

I'm very surprised by the number of posts that have ranted about Open/Close source, GPL/taint issues etc. This is not about source code it is about making Linux usable by the masses. It may be technically superior to follow the current model, but if the barrier to entry is very high (and it is!) then the project will continue to be a niche project. A binary model doesn't alter the community or the benefits of public source code. I agree that it is an extra interface and will carry a performance hit - I think this is worth it. Windows has many faults but drivers are often compatible across major releases and VERY compatible across minor releases. It is no accident that it has 90% of the desktop market. If we are going to improve this situation this issue MUST be confronted.

Quoted 5 lines

I am currently collating the arguments for and (mostly) against the idea. If I don't get flamed in the meantime I may come back with more...

James

The problem with Windows users is not that they are stupid or even uneducated. It's just that they have been taught that using a widely-used operating system that is defective in design and implementation is the way that operating systems should be.

They have been taught that bugs are normal. "Every program has bugs. It is impossible to check all possible execution paths to verify that there are no bugs, etc." This kind of teaching comes about when the teachers know little or nothing about their subjects and simply parrot what they have read in literature that, in many cases, has been written by the very persons who are incapable of writing bug-free code.

They have been taught that the secret inner workings of the kernel are best treated like the objects of an object- oriented design. In fact, they are taught that it's harmful for a programmer, much less a user, to understand the underlying workings of the operating system. This is taught because Microsoft doesn't want you to know what an abysmal abortion the operating system is.

Before Microsoft, nobody would dare sell a product that contained no warranty at all. Somehow, Microsoft has taught its customers that they should never expect software to actually work. Somehow, their lawyers have replaced the usual; "We warrant this product to be free of defects in workmanship and design for a period ..." to a disclaimer that many persons think is some kind of a warranty. In most cases, you can't even take a defective CD, defective because it can't be read, back to the vendor without encountering; "On it's software. Nobody warrants that!"

You can thank Microsoft for this.

There have been billions and billions of dollars of lost productivity in industry because of this defective Operating System. In one company alone, there was over one million dollars lost last year to defective software. You can look at the financial filings of many of the publically-traded companies and see write- offs due to defective software in this order of magnitude. Multiply that by the number of companies in the world to get the big picture.

And, somehow, companies still keep using that garbage!

Linux is something different. It strives for perfection. There is no way in hell that you are going to add some Microsoft-compatible driver interface to Linux. There are no drivers that could ever work on Windows and somehow work on Linux. These two systems are mutually exclusive, Alpha-Omega, 0->inf, good-evil, absolutely the antithesis of each other. I hear that's why Microsoft is attempting to kill Linux by funding the SCO lawsuit (check this week's EETimes, I didn't make it up).

Now, you propose to introduce a driver interface that is defective in concept. You propose this because you just don't get it. You just don't know anything about Operating Systems and you just don't know anything about Linux.

It may not be your fault. There are lots of people who haven't a clue because they have been taught things that are simply not true at all. And, once you repeat a falsehood enough times it becomes accepted as fact.

Before you can become qualified to propose a different driver interface, you need to learn about Operating Systems. I know that you do not know anything about Operating Systems in general, because of your proposal.

I suggest that you read a book like "Developing Your Own 32-bit Operating System", Burges, H.W.Sams, ISBN 0-627-30655-7 This is an interesting book because it is not about Windows and it's not about Linux. It's about a roll-your-own Operating System. It even comes with a CD and you can boot a home-grown system on your PC.

Now, I don't care if you studied Operating Systems in College. In fact, that just might be the reason why you don't know what you are talking about. Most such college courses in this subject are absolute crap, written by Masters candidates who learned a bunch of words and coined a few of their own.

After you learn about Operating Systems, then you might be able to add some new capability to Linux. You know, they accept patches here. If you've got a better way, you make a patch and we'll all try it. It's really that simple.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.

#13 lore raw

This is exactly the kind of FUD that is slowing Linux development and preventing wider use. Windows, for all its faults is a VERY BIG commercial success. You (and I) may believe that MS have persued some pretty bad practises to get where they are but the FACT is they are there and YOU are here. You may (I don't) believe that Windows is inherently unstable. This is FUD. It mostly works, sometimes it doesn't, but in total the number of working hours of PRODUCTIVE use from it is many orders of magnitude greater. Multiple the number of Windows users in the world by their working time and then do the same for Linux!

I have not proposed a driver model that is compatible with the Windows DDK. This is pure invention from the usual school of 'Windows v Linux, Linux is better because we made it'. The Linux driver model could be much better and hence the OS could escape the niche box it currently is in. Please ask Joe User how he feels about rebuilding his whole OS to add IP6 support to an existing stable system etc.

You have accused me of not knowing anything about OS design. I don't what your knowledge is, so I won't try and score points by telling you about mine - what I do know is that you obviously don't appreciate what is holding Linux back - You.

James

Quoted 115 lines · you
Quoted 15 lines · James Clark

Thank you for this (and the few other) sensible appraisal of my 'proposal'.

I'm very surprised by the number of posts that have ranted about Open/Close source, GPL/taint issues etc. This is not about source code it is about making Linux usable by the masses. It may be technically superior to follow the current model, but if the barrier to entry is very high (and it is!) then the project will continue to be a niche project. A binary model doesn't alter the community or the benefits of public source code. I agree that it is an extra interface and will carry a performance hit - I think this is worth it. Windows has many faults but drivers are often compatible across major releases and VERY compatible across minor releases. It is no accident that it has 90% of the desktop market. If we are going to improve this situation this issue MUST be confronted.

Quoted 4 lines

I am currently collating the arguments for and (mostly) against the idea. If I don't get flamed in the meantime I may come back with more...

James

The problem with Windows users is not that they are stupid or even uneducated. It's just that they have been taught that using a widely-used operating system that is defective in design and implementation is the way that operating systems should be.

They have been taught that bugs are normal. "Every program has bugs. It is impossible to check all possible execution paths to verify that there are no bugs, etc." This kind of teaching comes about when the teachers know little or nothing about their subjects and simply parrot what they have read in literature that, in many cases, has been written by the very persons who are incapable of writing bug-free code.

They have been taught that the secret inner workings of the kernel are best treated like the objects of an object- oriented design. In fact, they are taught that it's harmful for a programmer, much less a user, to understand the underlying workings of the operating system. This is taught because Microsoft doesn't want you to know what an abysmal abortion the operating system is.

Before Microsoft, nobody would dare sell a product that contained no warranty at all. Somehow, Microsoft has taught its customers that they should never expect software to actually work. Somehow, their lawyers have replaced the usual; "We warrant this product to be free of defects in workmanship and design for a period ..." to a disclaimer that many persons think is some kind of a warranty. In most cases, you can't even take a defective CD, defective because it can't be read, back to the vendor without encountering; "On it's software. Nobody warrants that!"

You can thank Microsoft for this.

There have been billions and billions of dollars of lost productivity in industry because of this defective Operating System. In one company alone, there was over one million dollars lost last year to defective software. You can look at the financial filings of many of the publically-traded companies and see write- offs due to defective software in this order of magnitude. Multiply that by the number of companies in the world to get the big picture.

And, somehow, companies still keep using that garbage!

Linux is something different. It strives for perfection. There is no way in hell that you are going to add some Microsoft-compatible driver interface to Linux. There are no drivers that could ever work on Windows and somehow work on Linux. These two systems are mutually exclusive, Alpha-Omega, 0->inf, good-evil, absolutely the antithesis of each other. I hear that's why Microsoft is attempting to kill Linux by funding the SCO lawsuit (check this week's EETimes, I didn't make it up).

Now, you propose to introduce a driver interface that is defective in concept. You propose this because you just don't get it. You just don't know anything about Operating Systems and you just don't know anything about Linux.

It may not be your fault. There are lots of people who haven't a clue because they have been taught things that are simply not true at all. And, once you repeat a falsehood enough times it becomes accepted as fact.

Before you can become qualified to propose a different driver interface, you need to learn about Operating Systems. I know that you do not know anything about Operating Systems in general, because of your proposal.

I suggest that you read a book like "Developing Your Own 32-bit Operating System", Burges, H.W.Sams, ISBN 0-627-30655-7 This is an interesting book because it is not about Windows and it's not about Linux. It's about a roll-your-own Operating System. It even comes with a CD and you can boot a home-grown system on your PC.

Now, I don't care if you studied Operating Systems in College. In fact, that just might be the reason why you don't know what you are talking about. Most such college courses in this subject are absolute crap, written by Masters candidates who learned a bunch of words and coined a few of their own.

After you learn about Operating Systems, then you might be able to add some new capability to Linux. You know, they accept patches here. If you've got a better way, you make a patch and we'll all try it. It's really that simple.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.

#14 lore raw
Quoted 6 lines · James Clark

I have not proposed a driver model that is compatible with the Windows DDK. This is pure invention from the usual school of 'Windows v Linux, Linux is better because we made it'. The Linux driver model could be much better and hence the OS could escape the niche box it currently is in. Please ask Joe User how he feels about rebuilding his whole OS to add IP6 support to an existing stable system etc.

Joe User got IPV6 from his vendor as a standard component, and if he didn't the large number of app patches his old distro need outweigh the kernel.

However for drivers its the same - its a _source_ level interface.

For example

spin_lock(&lock)

compiles to different things for uniprocessor/SMP kernels and the difference is worth real speed. So your binary interface roughly speaking depends on

- core options selected
- compiler (gcc2 v gcc3)
- SMP v UP
- Highmem v non highmem
- CPU target type
- 4G/4G split in 2.6 case

and a few more, while your source interface is pretty stable.

So what does that mean for someone adding a module

1. It needs compiling
2. If you want trivial end user ease then you need to wrap the
compilation up as part of the stuff the user never sees.

#15 lore raw
In reply to James Clark

Hello!

Quoted 2 lines

It mostly works, sometimes it doesn't, but in total the number of working hours of PRODUCTIVE use from it is many orders of magnitude greater.

Maybe the other people working on Linux feel different, but I just don't care about the masses and about anybody's commercial success. If they like using Windows, well, they deserve it. I'm helping to create a system _I_ and the people around me like.

About drivers: People around me who are using Windows do have many problems (want to use three different USB scanners simultaneously? eh, forget about that), people using Linux have slightly less or maybe the same amount of problems, but guess what -- for the Linux users there usually is somebody around who knows how to fix the things while Windows users are helplessly reinstalling their binary-only stuff nobody really understands. That's a real story and I guess it's a very typical one. And it's the reason why almost nobody here likes binary-only drivers.

Quoted 2 lines

Multiple the number of Windows users in the world by their working time and then do the same for Linux!

Well, you can multiply the number of insects in this universe by their working time and get an even larger number, but does that mean anything except you are skilled in arithmetic?

Have a nice fortnight

Signature · 3 lines
Martin `MJ' Mares   <[email protected]>   http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
First law of socio-genetics: Celibacy is not hereditary.
#16 lore raw
In reply to James Clark
Quoted 5 lines · James Clark

This is exactly the kind of FUD that is slowing Linux development and preventing wider use. Windows, for all its faults is a VERY BIG commercial success. You (and I) may believe that MS have persued some pretty bad practises to get where they are but the FACT is they are there and YOU are here. You may (I don't) believe that Windows is inherently unstable. This is FUD. It mostly works, sometimes it doesn't, but in total the number of working hours of PRODUCTIVE use from it is many orders of magnitude greater. Multiple the number of Windows users in the world by their working time and then do the same for Linux!

I have not proposed a driver model that is compatible with the Windows DDK. This is pure invention from the usual school of 'Windows v Linux, Linux is better because we made it'. The Linux driver model could be much better and hence the OS could escape the niche box it currently is in. Please ask Joe User how he feels about rebuilding his whole OS to add IP6 support to an existing stable system etc.

If i didn't know better I would say you haven't even tried linux. Joe User doesn't have to recompile anything. If the distribution he is using is any good (and most are) there is no need to recompile anything, it's already there as a module.

Quoted 6 lines

You have accused me of not knowing anything about OS design. I don't what your knowledge is, so I won't try and score points by telling you about mine - what I do know is that you obviously don't appreciate what is holding Linux back - You.

James

Most kernel developers don't get paid for what they do, they do it for fun and prestige. Reaching "the masses" isn't necessary the goal.

Quoted 132 lines · you
Quoted 116 lines · James Clark
Quoted 17 lines

Thank you for this (and the few other) sensible appraisal of my 'proposal'.

I'm very surprised by the number of posts that have ranted about Open/Close source, GPL/taint issues etc. This is not about source code it is about making Linux usable by the masses. It may be technically superior to follow the current model, but if the barrier to entry is very high (and it is!) then the project will continue to be a niche project. A binary model doesn't alter the community or the benefits of public source code. I agree that it is an extra interface and will carry a performance hit - I think this is worth it. Windows has many faults but drivers are often compatible across major releases and VERY compatible across minor releases. It is no accident that it has 90% of the desktop market. If we are going to improve this situation this issue MUST be confronted.

Quoted 6 lines

I am currently collating the arguments for and (mostly) against the idea. If I don't get flamed in the meantime I may come back with more...

James

The problem with Windows users is not that they are stupid or even uneducated. It's just that they have been taught that using a widely-used operating system that is defective in design and implementation is the way that operating systems should be.

They have been taught that bugs are normal. "Every program has bugs. It is impossible to check all possible execution paths to verify that there are no bugs, etc." This kind of teaching comes about when the teachers know little or nothing about their subjects and simply parrot what they have read in literature that, in many cases, has been written by the very persons who are incapable of writing bug-free code.

They have been taught that the secret inner workings of the kernel are best treated like the objects of an object- oriented design. In fact, they are taught that it's harmful for a programmer, much less a user, to understand the underlying workings of the operating system. This is taught because Microsoft doesn't want you to know what an abysmal abortion the operating system is.

Before Microsoft, nobody would dare sell a product that contained no warranty at all. Somehow, Microsoft has taught its customers that they should never expect software to actually work. Somehow, their lawyers have replaced the usual; "We warrant this product to be free of defects in workmanship and design for a period ..." to a disclaimer that many persons think is some kind of a warranty. In most cases, you can't even take a defective CD, defective because it can't be read, back to the vendor without encountering; "On it's software. Nobody warrants that!"

You can thank Microsoft for this.

There have been billions and billions of dollars of lost productivity in industry because of this defective Operating System. In one company alone, there was over one million dollars lost last year to defective software. You can look at the financial filings of many of the publically-traded companies and see write- offs due to defective software in this order of magnitude. Multiply that by the number of companies in the world to get the big picture.

And, somehow, companies still keep using that garbage!

Linux is something different. It strives for perfection. There is no way in hell that you are going to add some Microsoft-compatible driver interface to Linux. There are no drivers that could ever work on Windows and somehow work on Linux. These two systems are mutually exclusive, Alpha-Omega, 0->inf, good-evil, absolutely the antithesis of each other. I hear that's why Microsoft is attempting to kill Linux by funding the SCO lawsuit (check this week's EETimes, I didn't make it up).

Now, you propose to introduce a driver interface that is defective in concept. You propose this because you just don't get it. You just don't know anything about Operating Systems and you just don't know anything about Linux.

It may not be your fault. There are lots of people who haven't a clue because they have been taught things that are simply not true at all. And, once you repeat a falsehood enough times it becomes accepted as fact.

Before you can become qualified to propose a different driver interface, you need to learn about Operating Systems. I know that you do not know anything about Operating Systems in general, because of your proposal.

I suggest that you read a book like "Developing Your Own 32-bit Operating System", Burges, H.W.Sams, ISBN 0-627-30655-7 This is an interesting book because it is not about Windows and it's not about Linux. It's about a roll-your-own Operating System. It even comes with a CD and you can boot a home-grown system on your PC.

Now, I don't care if you studied Operating Systems in College. In fact, that just might be the reason why you don't know what you are talking about. Most such college courses in this subject are absolute crap, written by Masters candidates who learned a bunch of words and coined a few of their own.

After you learn about Operating Systems, then you might be able to add some new capability to Linux. You know, they accept patches here. If you've got a better way, you make a patch and we'll all try it. It's really that simple.

Quoted 6 lines

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#17 lore raw
In reply to James Clark
Quoted 4 lines · James Clark

FUD. It mostly works, sometimes it doesn't, but in total the number of working hours of PRODUCTIVE use from it is many orders of magnitude greater. Multiple the number of Windows users in the world by their working time and then do the same for Linux!

So if 500 million people are productive 60% of the time and hosed 40% of the time, and 5 million people are productive 95% of the time, the 60/40 model is better because 60% of 500M is more than 95% of 5M?

What's wrong with this picture?

Quoted 3 lines

hence the OS could escape the niche box it currently is in. Please ask Joe User how he feels about rebuilding his whole OS to add IP6 support to an existing stable system etc.

Ask Joe User how he feels about NOT being able to add IPv6 support to his existing system until his vendor says they'll do it for him, and then look at when Linux had support.

http://www.ipv6.org/impl/linux.html
http://www.ipv6.org/impl/windows.html

And most important, google around for +ipv6 +"craig metz", and look at when *he* did the IPv6 work - and you were free to put the patches on your system as soon as he posted them.

Now as you were saying?

#18 lore raw
Quoted 3 lines · Valdis Kletnieks

So if 500 million people are productive 60% of the time and hosed 40% of the time, and 5 million people are productive 95% of the time, the 60/40 model is better because 60% of 500M is more than 95% of 5M?

This is a good example of the kind of rubbish that is sometimes talked around here. I've lost count of the number of times I've heard the 'Windows is SO unstable argument' it almost seems like a religion. I would agree with what you have said if Windows was actually unusable 40% of the time. Do you really believe this figure? In reality it is much better than that as plainly the majority of the WORLD are using it. I love Linux but I also use Windows. Sorry to break your delusion, it ain't that bad.

Quoted 3 lines

Ask Joe User how he feels about NOT being able to add IPv6 support to his existing system until his vendor says they'll do it for him, and then look at when Linux had support.

Its very true that in the Windows world you have to wait for Micro$oft sometimes, it is even true that they probably hold back features so that can put them in the next release and get you to pay for them. Why is this any worse than expecting Joe User, who is a 'user' and not a 'developer' to rebuild the most important bits of his OS and risk breaking the whole lot.

This is not about Windows v Linux so please stop compraring what I have proposed to Windows. This debate should be about Performance v Usability. Source interfaces have ultimate performance, nobody has suggested, yet, that they are easier for Joe User than a binary interface.

James

Quoted 28 lines · you
Quoted 4 lines · James Clark

FUD. It mostly works, sometimes it doesn't, but in total the number of working hours of PRODUCTIVE use from it is many orders of magnitude greater. Multiple the number of Windows users in the world by their working time and then do the same for Linux!

So if 500 million people are productive 60% of the time and hosed 40% of the time, and 5 million people are productive 95% of the time, the 60/40 model is better because 60% of 500M is more than 95% of 5M?

What's wrong with this picture?

Quoted 3 lines

hence the OS could escape the niche box it currently is in. Please ask Joe User how he feels about rebuilding his whole OS to add IP6 support to an existing stable system etc.

Ask Joe User how he feels about NOT being able to add IPv6 support to his existing system until his vendor says they'll do it for him, and then look at when Linux had support.

http://www.ipv6.org/impl/linux.html
http://www.ipv6.org/impl/windows.html

And most important, google around for +ipv6 +"craig metz", and look at when *he* did the IPv6 work - and you were free to put the patches on your system as soon as he posted them.

Now as you were saying?

#19 lore raw
Quoted 24 lines · James Clark
Quoted 3 lines · Valdis Kletnieks

So if 500 million people are productive 60% of the time and hosed 40% of the time, and 5 million people are productive 95% of the time, the 60/40 model is better because 60% of 500M is more than 95% of 5M?

This is a good example of the kind of rubbish that is sometimes talked around here. I've lost count of the number of times I've heard the 'Windows is SO unstable argument' it almost seems like a religion. I would agree with what you have said if Windows was actually unusable 40% of the time. Do you really believe this figure? In reality it is much better than that as plainly the majority of the WORLD are using it. I love Linux but I also use Windows. Sorry to break your delusion, it ain't that bad.

Quoted 3 lines

Ask Joe User how he feels about NOT being able to add IPv6 support to his existing system until his vendor says they'll do it for him, and then look at when Linux had support.

Its very true that in the Windows world you have to wait for Micro$oft sometimes, it is even true that they probably hold back features so that can put them in the next release and get you to pay for them. Why is this any worse than expecting Joe User, who is a 'user' and not a 'developer' to rebuild the most important bits of his OS and risk breaking the whole lot.

Quoted 5 lines

This is not about Windows v Linux so please stop compraring what I have proposed to Windows. This debate should be about Performance v Usability. Source interfaces have ultimate performance, nobody has suggested, yet, that they are easier for Joe User than a binary interface.

Right. Not trying to get involved in this mess [8)], but there was a few other comments that was less linux/windows, but more valid ... what about responding to them? Could be interesting to hear what you have to say ...

Quoted 39 lines

James

Quoted 20 lines · you
Quoted 4 lines · James Clark

FUD. It mostly works, sometimes it doesn't, but in total the number of working hours of PRODUCTIVE use from it is many orders of magnitude greater. Multiple the number of Windows users in the world by their working time and then do the same for Linux!

So if 500 million people are productive 60% of the time and hosed 40% of the time, and 5 million people are productive 95% of the time, the 60/40 model is better because 60% of 500M is more than 95% of 5M?

What's wrong with this picture?

Quoted 3 lines

hence the OS could escape the niche box it currently is in. Please ask Joe User how he feels about rebuilding his whole OS to add IP6 support to an existing stable system etc.

Ask Joe User how he feels about NOT being able to add IPv6 support to his existing system until his vendor says they'll do it for him, and then look at when Linux had support.

Quoted 8 lines

http://www.ipv6.org/impl/linux.html
http://www.ipv6.org/impl/windows.html

And most important, google around for +ipv6 +"craig metz", and look at when *he* did the IPv6 work - and you were free to put the patches on your system as soon as he posted them.

Now as you were saying?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 1 line
Martin Schlemmer
#20 lore raw
In reply to James Clark
Quoted 9 lines · James Clark
Quoted 3 lines · Valdis Kletnieks

So if 500 million people are productive 60% of the time and hosed 40% of the time, and 5 million people are productive 95% of the time, the 60/40 model is better because 60% of 500M is more than 95% of 5M?

This is a good example of the kind of rubbish that is sometimes talked around here. I've lost count of the number of times I've heard the 'Windows is SO unstable argument' it almost seems like a religion. I would agree with what you have said if Windows was actually unusable 40% of the time. Do you really believe this figure? In reality it is much better than that as plainly the majority of the WORLD are using it. I love Linux but I also use Windows. Sorry to break your delusion, it ain't that bad.

The only windows system that I have seen that was reliable (unless the people there were lying to me) was a big ibm netfinity system. I believe it was stable because it didn't use any extra harware or drivers except what ibm had installed on the box.

What I'm saying is that most of the problems with windows are from flakey, half-baked drivers and dll's form third parties. I've got no hard numbers, just my personal experiences.

Binary onlyt drivers are bad. Source drivers are good. THat's just the way it is.

-Dale

Signature · 2 lines
Dale P. Smith
dsmith at actron dot com
#21 lore raw
Quoted 3 lines · Dale P. Smith

The only windows system that I have seen that was reliable (unless the people there were lying to me) was a big ibm netfinity system. I believe it was stable because it didn't use any extra harware or drivers except what ibm had installed on the box.

I dunno I had Win2k running with only 2 crashes for 3 years on a Dell OptiPlex GX300 866MHz SMP system. Believe it or not for the first 2 years I never had a full system crash. I left it on for months at a time. That doesn't mean windows is stable though. It means for my particular setup it was. I'm probably one of the few people I know on campus who haven't had to had to format there windows
and start over several times. The biggest problem is the windows
registry, once it becomes corrupt unless you have a backup you've lost all your settings. This is horrible by design. Any minor corruption or registry permissions problems can cause a system to go down faster than Jennifer Lopez.

Quoted 2 lines

What I'm saying is that most of the problems with windows are from flakey, half-baked drivers and dll's form third parties. I've got no hard numbers, just my personal experiences.

All my problems have been flakey, half-baked drivers and DLLs from Microsoft, so I cannot relate.

Quoted 2 lines

Binary onlyt drivers are bad. Source drivers are good. THat's just the way it is.

Agreed.

Quoted 2 lines

-Dale

#22 lore raw
In reply to James Clark
Quoted 6 lines · James Clark
Quoted 3 lines · Valdis Kletnieks

So if 500 million people are productive 60% of the time and hosed 40% of the time, and 5 million people are productive 95% of the time, the 60/40 model is better because 60% of 500M is more than 95% of 5M?

Quoted 8 lines

This is a good example of the kind of rubbish that is sometimes talked around here. I've lost count of the number of times I've heard the 'Windows is SO unstable argument' it almost seems like a religion. I would agree with what you have said if Windows was actually unusable 40% of the time. Do you really believe this figure? In reality it is much better than that as plainly the majority of the WORLD are using it. I love Linux but I also use Windows. Sorry to break your delusion, it ain't that bad.

I sure wish it was rubbish. In my other life I write music. So, I bought Cakewalk Software so I could record and edit music I play on my MIDI Grand Piano. Unfortunately this only worked with Windows.

I wanted to have the most reliable machine possible so I installed windows in a machine that I had been running Linux on for about two years. It was (is) a dual Pentium 400 MHz machine with a 100 MHz front-side bus. This is a Tyan "Thunder" board. This is not the latest-and-greatest. Just a good "old" reliable machine. The machine had two SCSI disks with an Adaptec controller.

Windows installed fine. It even seemed to work. I recorded and edited many compositions. I also backed up my files to a SCSI tape using the Windows backup utility.

After several months of use, the machine would not boot anymore. I had to reinstall windows from scratch since the partition was corrupt and the distribution CD would not fix or install anything over it. Since I didn't want to lose everything on the disk, I bought another one, thinking I could always copy my stuff from the original. Guess again. The original disk was so destroyed that Linux wouldn't even recognize it. Even as a raw device I was unable to recover any of my composition data.

Not to worry. I still have the backups. Guess again, Windows would not read the backup data. I had just lost several months of my life and, incidentally, some piano playing by another pianist who will become famous someday. All lost. All gone.

I eventually replaced all my compositions, except those played by the other pianist. This means that I had to practice over 40 compositions over and over again, then record them again. This is a lot of "hurt" over many months.

Then the same thing happened again! The machine would no longer boot and the file-systems were totally trashed. Also, I had bought an external Fire-wire drive to which I wrote the backup files. Again, after completely installing everything again, I was unable to recover any of my data from the backup files.

To make an long-story short, the "solution", proposed by Microsoft was to remove one of the CPUs. They said; "Windows is too powerful. With that extra CPU, you are over-powering the machine."

This is not an isolated incident. Every Engineer I have ever worked with (or even talked to) has similar horror stories. Every Writer that I know of who has attempted to use Windows to keep their life-long dreams alive, has similar horror stories. Every Artist that I know, who used Windows has similar stories. They have all migrated to Apple. They were not of the "Apple Generation" either. They all started out using Windows because that's what "everybody" used. They went to Apple because it doesn't destroy their work.

Most persons who use Linux have similar horror stories about Windows. The difference, here, being that they thought that no widely-used Operating System could be as bad as they found it to be. Instead, they for the most part, though that their problems were isolated incidents. Once they started communicating, it became obvious that practically everybody has problems with Windows. In the days where VAXen were the "Engineering" computers, we had 200 Engineers, two computers, and one System Manager. Now, those 200 Engineers require 30 "Windows Administrators" for support, just to be able to share project directories.

They spend their time reinstalling Windows Software.

Cakewalk recently released an Apple version of "Home Studio". I'm going to buy and Apple and convert the Windows machine back to Linux. I wish they had ported their stuff to Linux. I would still have some hair left.

So, if you think Windows "works", you just haven't any experience. In a year or two, maximum, if you are trying to use a Windows machine for any serious work, you will probably be planning a trip to Redmond, carrying an axe.

When you talk about 40% or even 10% failure rate, you are talking nonsense. A computing machine must never have any failures that an end-user could detect. It's not quite six-sigma, but to the end-user it should seem like that. Any real operating system will not fail as long as the hardware doesn't fail. No version of Windows qualifies.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.

#23 lore raw

My original thread was called 'Linux Kernel Performance v Usability'. This has nothing to do with Windows.

James

Quoted 103 lines · you
Quoted 5 lines · James Clark
Quoted 3 lines · Valdis Kletnieks

So if 500 million people are productive 60% of the time and hosed 40% of the time, and 5 million people are productive 95% of the time, the 60/40 model is better because 60% of 500M is more than 95% of 5M?

Quoted 8 lines

This is a good example of the kind of rubbish that is sometimes talked around here. I've lost count of the number of times I've heard the 'Windows is SO unstable argument' it almost seems like a religion. I would agree with what you have said if Windows was actually unusable 40% of the time. Do you really believe this figure? In reality it is much better than that as plainly the majority of the WORLD are using it. I love Linux but I also use Windows. Sorry to break your delusion, it ain't that bad.

I sure wish it was rubbish. In my other life I write music. So, I bought Cakewalk Software so I could record and edit music I play on my MIDI Grand Piano. Unfortunately this only worked with Windows.

I wanted to have the most reliable machine possible so I installed windows in a machine that I had been running Linux on for about two years. It was (is) a dual Pentium 400 MHz machine with a 100 MHz front-side bus. This is a Tyan "Thunder" board. This is not the latest-and-greatest. Just a good "old" reliable machine. The machine had two SCSI disks with an Adaptec controller.

Windows installed fine. It even seemed to work. I recorded and edited many compositions. I also backed up my files to a SCSI tape using the Windows backup utility.

After several months of use, the machine would not boot anymore. I had to reinstall windows from scratch since the partition was corrupt and the distribution CD would not fix or install anything over it. Since I didn't want to lose everything on the disk, I bought another one, thinking I could always copy my stuff from the original. Guess again. The original disk was so destroyed that Linux wouldn't even recognize it. Even as a raw device I was unable to recover any of my composition data.

Not to worry. I still have the backups. Guess again, Windows would not read the backup data. I had just lost several months of my life and, incidentally, some piano playing by another pianist who will become famous someday. All lost. All gone.

I eventually replaced all my compositions, except those played by the other pianist. This means that I had to practice over 40 compositions over and over again, then record them again. This is a lot of "hurt" over many months.

Then the same thing happened again! The machine would no longer boot and the file-systems were totally trashed. Also, I had bought an external Fire-wire drive to which I wrote the backup files. Again, after completely installing everything again, I was unable to recover any of my data from the backup files.

To make an long-story short, the "solution", proposed by Microsoft was to remove one of the CPUs. They said; "Windows is too powerful. With that extra CPU, you are over-powering the machine."

This is not an isolated incident. Every Engineer I have ever worked with (or even talked to) has similar horror stories. Every Writer that I know of who has attempted to use Windows to keep their life-long dreams alive, has similar horror stories. Every Artist that I know, who used Windows has similar stories. They have all migrated to Apple. They were not of the "Apple Generation" either. They all started out using Windows because that's what "everybody" used. They went to Apple because it doesn't destroy their work.

Most persons who use Linux have similar horror stories about Windows. The difference, here, being that they thought that no widely-used Operating System could be as bad as they found it to be. Instead, they for the most part, though that their problems were isolated incidents. Once they started communicating, it became obvious that practically everybody has problems with Windows. In the days where VAXen were the "Engineering" computers, we had 200 Engineers, two computers, and one System Manager. Now, those 200 Engineers require 30 "Windows Administrators" for support, just to be able to share project directories.

They spend their time reinstalling Windows Software.

Cakewalk recently released an Apple version of "Home Studio". I'm going to buy and Apple and convert the Windows machine back to Linux. I wish they had ported their stuff to Linux. I would still have some hair left.

So, if you think Windows "works", you just haven't any experience. In a year or two, maximum, if you are trying to use a Windows machine for any serious work, you will probably be planning a trip to Redmond, carrying an axe.

When you talk about 40% or even 10% failure rate, you are talking nonsense. A computing machine must never have any failures that an end-user could detect. It's not quite six-sigma, but to the end-user it should seem like that. Any real operating system will not fail as long as the hardware doesn't fail. No version of Windows qualifies.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.

#24 lore raw
In reply to James Clark
Quoted 4 lines · James Clark

This is not about Windows v Linux so please stop compraring what I have proposed to Windows. This debate should be about Performance v Usability. Source interfaces have ultimate performance, nobody has suggested, yet, that they are easier for Joe User than a binary interface.

Here is one thing we don't have standardized across the entire Linux distribution landscape.

What you need is a project that will take the top 10 distributions, and do this however each distribution does their thing:

o identify the current kernel running (you're going to use the kernel you're running, right?)

o download the kernel source for the running kernel

o install the source in some temporary location

o compile against the downloaded kernel source

o install the module under /lib/modules

o load the module (with the corect optional parameters)

Now what we need is someone to create the project, and get the community to point to that project for source available external driver modules.

And look! No kernel modifications!

#25 lore raw
In reply to James Clark
Quoted 9 lines · James Clark
Quoted 3 lines

So if 500 million people are productive 60% of the time and hosed 40% of the time, and 5 million people are productive 95% of the time, the 60/40 model is better because 60% of 500M is more than 95% of 5M?

This is a good example of the kind of rubbish that is sometimes talked around

here. I've lost count of the number of times I've heard the 'Windows is SO unstable argument' it almost seems like a religion. I would agree with what you have said if Windows was actually unusable 40% of the time.

Quoted 4 lines · What you

FUD. It mostly works, sometimes it doesn't, but in total the number of

Quoted 3 lines

working hours of PRODUCTIVE use from it is many orders of magnitude greater. Multiple the number of Windows users in the world by their working time and then do the same for Linux!

Oh.. so now you're complaining that I pointed out that even a system that's down 40% of the time meets *YOUR* criteria if enough more people run it?

In fact, if the number of Windows users is 100 times the number of Linux users, and Linux is 98% reliable, then Windows only needs to make about 2% reliable to win by your criteria. OK, you want to complain about the 100? Make it 500M windows and 50M linux, and Linux 98% reliable, then Windows only needs to make 10% uptime to win by your criteria.

My point is that your criteria of "total aggregate uptime" doesn't prove anything between diddly and squat about the actual reliability of the system.

#26 lore raw
Quoted 2 lines · In article <[email protected]> you wrote:

My point is that your criteria of "total aggregate uptime" doesn't prove anything between diddly and squat about the actual reliability of the system.

Even if this is a not very on-topic discussion, and especially because I do not agree about Windows beeing unstable at all:

- how about agregating the downtimes as the cummulative lost time by instability.

Greetings
Bernd

Signature · 2 lines
eckes privat - http://www.eckes.org/
Project Freefire - http://www.freefire.org/
#27 lore raw
In reply to Richard B. Johnson

I just have one quick question about all of this:

People mention that driver interfaces don't change much in stable releases, but if memory serves, symbol versioning information changes with each minor release, requiring a recompile of modules.

Would it be possible to have a driver module which can be dropped into, say, 2.6.17 that can also be dropped into 2.6.18 as long as the interface doesn't change?

#28 lore raw
Quoted 10 lines · Timothy Miller

I just have one quick question about all of this:

People mention that driver interfaces don't change much in stable releases, but if memory serves, symbol versioning information changes with each minor release, requiring a recompile of modules.

Would it be possible to have a driver module which can be dropped into, say, 2.6.17 that can also be dropped into 2.6.18 as long as the interface doesn't change?

Short answer, YES. Anything that can be done is possible. The problem is that different kernel versions end up with different structure members, etc. So, you can't use code for 2.2.xxx in 2.4.xx because, amongst other things, the first element in 'struct file_operations' was added and the others moved up.

Now, you can make a different module interface that maintains a compatibility level ABI. This has been discussed. Unfortunately, this adds code in the execution path. This extra code gets executed every time the module code is accessed. The result being that the module can't possibly operate as fast as it would if there were no such compatibility layer(s). It might be "good enough", but it is unlikely that the module contributors/maintainers would allow such an interface because the loss of performance is measurable and there has been no requirement to trade-off performance for anything (your and my convenience doesn't count, those are not technical issues).

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.

#29 lore raw

Has anyone ever done any work to quantify what the loss in performance might be with a binary interface?

James

Quoted 41 lines · Richard B. Johnson
Quoted 9 lines · Timothy Miller

I just have one quick question about all of this:

People mention that driver interfaces don't change much in stable releases, but if memory serves, symbol versioning information changes with each minor release, requiring a recompile of modules.

Would it be possible to have a driver module which can be dropped into, say, 2.6.17 that can also be dropped into 2.6.18 as long as the interface doesn't change?

Short answer, YES. Anything that can be done is possible. The problem is that different kernel versions end up with different structure members, etc. So, you can't use code for 2.2.xxx in 2.4.xx because, amongst other things, the first element in 'struct file_operations' was added and the others moved up.

Now, you can make a different module interface that maintains a compatibility level ABI. This has been discussed. Unfortunately, this adds code in the execution path. This extra code gets executed every time the module code is accessed. The result being that the module can't possibly operate as fast as it would if there were no such compatibility layer(s). It might be "good enough", but it is unlikely that the module contributors/maintainers would allow such an interface because the loss of performance is measurable and there has been no requirement to trade-off performance for anything (your and my convenience doesn't count, those are not technical issues).

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#30 lore raw
Quoted 2 lines · James Clark

Has anyone ever done any work to quantify what the loss in performance might be with a binary interface?

See the UDI results.

greg k-h

#31 lore raw
In reply to Richard B. Johnson
Quoted 15 lines · Richard B. Johnson
Quoted 10 lines · Timothy Miller

I just have one quick question about all of this:

People mention that driver interfaces don't change much in stable releases, but if memory serves, symbol versioning information changes with each minor release, requiring a recompile of modules.

Would it be possible to have a driver module which can be dropped into, say, 2.6.17 that can also be dropped into 2.6.18 as long as the interface doesn't change?

Quoted 5 lines

Short answer, YES. Anything that can be done is possible. The problem is that different kernel versions end up with different structure members, etc. So, you can't use code for 2.2.xxx in 2.4.xx because, amongst other things, the first element in 'struct file_operations' was added and the others moved up.

That's all fine and dandy. When the kernel changes its interface, then you have to recompile (or rewrite) drivers. No problem. I'm just trying to avoid having to recompile drivers if the interface DOESN'T change.

Quoted 12 lines

Now, you can make a different module interface that maintains a compatibility level ABI. This has been discussed. Unfortunately, this adds code in the execution path. This extra code gets executed every time the module code is accessed. The result being that the module can't possibly operate as fast as it would if there were no such compatibility layer(s). It might be "good enough", but it is unlikely that the module contributors/maintainers would allow such an interface because the loss of performance is measurable and there has been no requirement to trade-off performance for anything (your and my convenience doesn't count, those are not technical issues).

I am not interested in adding additional layers of abstraction. At least not here. I do it plenty of other places, but that's not important right now. If someone else wants to make an abstraction layer (which seems to have been done here and there), then that's just fine, and I may or may not use it.

My point is that I'm not advocating any of the kruft associated with backward-compatible interfaces. I'm advocating not having to recompile only in the cases where the interface DOES NOT change.

Why? Because there are some advantages to being able to say that this one module can be dropped into any box running, for instance, 2.6.12 through 2.6.16, while the next module is used for 2.6.17 thru 2.6.22, etc.

For distributions, this can be helpful for drivers which are not in the mainline kernel. So, I'm not trying to necessarily find a way to help binary-only drivers (although it would, to some extent).

#32 lore raw
Quoted 3 lines · Timothy Miller

Why? Because there are some advantages to being able to say that this one module can be dropped into any box running, for instance, 2.6.12 through 2.6.16, while the next module is used for 2.6.17 thru 2.6.22, etc.

There are a SLEW of options that make this hard.

CONFIG_SMP - spinlocks get compiled in or not

CONFIG_SPINLOCK_DEBUGGING - changes the size of a spinlock and the behavior of spin_lock() and friend

All the HIGHMEM and various kernel/user split option - change the kernel virtual addresses and offsets

And these are just a few. The thing is, there isn't any way to catalog them all, because at any point, someone can add a CONFIG_FOO_DEBUG which changes the size of a struct foo and foo_op(). Then any module which uses a foo has to ALSO have FOO_DEBUG on. Modules and kernels must match up on ALL the options (or at least, all the ones that cross the kernel-module boundary).

This actually bit me just last week. I turn on spinlock debugging, and a module Oopses. I didn't recompile modules.

It sucks. I agree. Maybe there is an elegant way to checksum each functional interface and each datatype and typedef and each argument to each funtion and make it such that IFF they are all the same, the module will load. It's just not pretty.

Signature · 3 lines
Notice that as computers are becoming easier and easier to use,
suddenly there's a big market for "Dummies" books.  Cause and effect,
or merely an ironic juxtaposition of unrelated facts?
#33 lore raw
In reply to Timothy Miller
Quoted 47 lines · Timothy Miller
Quoted 15 lines · Richard B. Johnson
Quoted 10 lines · Timothy Miller

I just have one quick question about all of this:

People mention that driver interfaces don't change much in stable releases, but if memory serves, symbol versioning information changes with each minor release, requiring a recompile of modules.

Would it be possible to have a driver module which can be dropped into, say, 2.6.17 that can also be dropped into 2.6.18 as long as the interface doesn't change?

Quoted 5 lines

Short answer, YES. Anything that can be done is possible. The problem is that different kernel versions end up with different structure members, etc. So, you can't use code for 2.2.xxx in 2.4.xx because, amongst other things, the first element in 'struct file_operations' was added and the others moved up.

That's all fine and dandy. When the kernel changes its interface, then you have to recompile (or rewrite) drivers. No problem. I'm just trying to avoid having to recompile drivers if the interface DOESN'T change.

Quoted 12 lines

Now, you can make a different module interface that maintains a compatibility level ABI. This has been discussed. Unfortunately, this adds code in the execution path. This extra code gets executed every time the module code is accessed. The result being that the module can't possibly operate as fast as it would if there were no such compatibility layer(s). It might be "good enough", but it is unlikely that the module contributors/maintainers would allow such an interface because the loss of performance is measurable and there has been no requirement to trade-off performance for anything (your and my convenience doesn't count, those are not technical issues).

I am not interested in adding additional layers of abstraction. At least not here. I do it plenty of other places, but that's not important right now. If someone else wants to make an abstraction layer (which seems to have been done here and there), then that's just fine, and I may or may not use it.

Quoted 4 lines

My point is that I'm not advocating any of the kruft associated with backward-compatible interfaces. I'm advocating not having to recompile only in the cases where the interface DOES NOT change.

In those cases, you simply use "-f" on the insmod command line to force the loading of a module. We have that capability now. But, the offsets of things your module(s) access can, read will, be incompatible if the version changed. You "takes you chances and cross you fingers...." if you use the "-f" option.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.