State of the Union: Wireless
Quoted 7 lines
I don't like the idea of maintaining two of anything. What if I have two wireless interfaces, each using a different stack?
Performance--,
Kernel size++I get that it's hard to get everyone to agree on one stack or another, but we need to make the decision now because the longer we don't have a decision made (this includes maintaining two in-tree stacks) the longer it's going to take us to have serious / robust / reliable / consistent wireless support.
This is exactly the opposite of what Linus proposes in his management style document: "Avoid making decisions". At the moment, nobody seems to know what the "right" direction is, because the right direction is the one that will produce the better wireless support, and not the one that sounds better at the moment.
I therefore also vote for merging both stacks.
Quoted 1 line
We can always undo mistakes later, but we'll never get to that point if we don't start moving in one direction instead of ten.
You were right if there were ten, but there seem to be only two at the moment. One stack will survive and one will die. There's no point in deciding this now.
Tim
Quoted 8 lines · Tim Tassonis
...
Quoted 3 lines
We can always undo mistakes later, but
we'll never get to that point if we don't start moving in one direction instead of ten.You were right if there were ten, but there seem to be only two at the moment. One stack will survive and one will die. There's no point in deciding this now.
No, we'll end up with two stacks, some drivers using the first stack and some the second one.
You can't simply let one stack die because this would imply either rewriting all drivers using this stack or dropping support for some hardware.
Quoted 1 line
Tim
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 8 lines · Adrian Bunk
Quoted 3 lines · Tim Tassonis
...
Quoted 1 line
We can always undo mistakes later, but we'll never get to that point if we don't start moving in one direction instead of ten.
You were right if there were ten, but there seem to be only two at the moment. One stack will survive and one will die. There's no point in deciding this now.
No, we'll end up with two stacks, some drivers using the first stack and some the second one.
You can't simply let one stack die because this would imply either rewriting all drivers using this stack or dropping support for some hardware.
By "die", I didn't mean "delete it from kernel sources".
It is very probable that over time, the "winning" stack will contain most drivers for the most common hardware, and the "losing" one just a few obscure ones. The "losing" one will still be available for people using hardware only supported by that stack.
Like the OSS/Alsa or XFree3.x/XFree4.x situations.
Tim
Quoted 17 lines · Tim Tassonis
Quoted 9 lines · Adrian Bunk
Quoted 7 lines · Tim Tassonis
...
Quoted 3 lines
We can always undo mistakes later, but
we'll never get to that point if we don't start moving in one direction instead of ten.You were right if there were ten, but there seem to be only two at the moment. One stack will survive and one will die. There's no point in deciding this now.
Quoted 6 lines
No, we'll end up with two stacks, some drivers using the first stack and some the second one.
You can't simply let one stack die because this would imply either rewriting all drivers using this stack or dropping support for some hardware.
Quoted 8 lines
By "die", I didn't mean "delete it from kernel sources".
It is very probable that over time, the "winning" stack will contain most drivers for the most common hardware, and the "losing" one just a few obscure ones. The "losing" one will still be available for people using hardware only supported by that stack.
Like the OSS/Alsa or XFree3.x/XFree4.x situations.
And OSS/ALSA is an example why this is not a good thing:
- OSS in the kernel is unmaintained
- people forced to use OSS drivers can't use applications only supporting ALSA
In the OSS/ALSA case this was not avoidable since OSS was for a long time the sound system in the kernel, and ALSA came later.
But if you have the possibility to choose which stack to use at the beginning (as in the wireless case), the only reasonable solution is to choose _one_ stack.
Quoted 1 line
Tim
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 5 lines · Adrian Bunk
Quoted 1 line · Tim Tassonis
Like the OSS/Alsa or XFree3.x/XFree4.x situations.
And OSS/ALSA is an example why this is not a good thing:
- OSS in the kernel is unmaintained
Because it is dead, yes...
Quoted 2 lines
- people forced to use OSS drivers can't use applications only supporting ALSA
That is another problem. The problem is different API's. With networking drivers, that should really not be a problem once the device is up. You don't speak differently to different network devices, so applications will just do fine.
Quoted 1 line
But if you have the possibility to choose which stack to use at the beginning (as in the wireless case), the only reasonable solution is to choose _one_ stack.
... _if_ you have the possibility, yes. But you might end up having chosen the wrong one. There is a reason why two stacks exist.
Tim
Quoted 8 lines · Tim Tassonis
Quoted 5 lines · Adrian Bunk
Quoted 1 line · Tim Tassonis
Like the OSS/Alsa or XFree3.x/XFree4.x situations.
And OSS/ALSA is an example why this is not a good thing:
- OSS in the kernel is unmaintainedBecause it is dead, yes...
And this is exactly what you predicted for one of the merged stacks.
Quoted 7 lines
...
Quoted 3 lines
But if you have the possibility to choose which stack to use at the beginning (as in the wireless case), the only reasonable solution is to choose _one_ stack.
... _if_ you have the possibility, yes. But you might end up having chosen the wrong one. There is a reason why two stacks exist.
The decision was already in the past - there is one stack that is already merged.
The question is whether there is a different stack that is considered that much better that switching to this stack including converting all drivers is worth the effort.
In the short term, having different stacks with different features and deficites only creates confusion.
In the long term, different stacks in the kernel will be a maintenance nightmare.
Quoted 1 line
Tim
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 5 lines
I won't try to speak for Linus (perhaps he'd like to pipe up at some point), but I think you're pulling that concept wayy out of context here.
Quoting ManagementStyle:
Quoted 7 lines
Quoted 5 lines
Btw, another way to avoid a decision is to plaintively just whine "can't we just do both?" and look pitiful. Trust me, it works. If it's not clear which approach is better, they'll eventually figure it out. The answer may end up being that both teams get so frustrated by the situation that they just give up.
Built into that paragraph, I think, is the assumption that you never 'do both'.
Well, we'd have to ask Linus about this one. I think it can be a good idea to do both, if you're not sure which one is better.
Quoted 2 lines
Also, referring to OSS/Alsa is just a great way to illustrate the problem with your idea. There is, today, finally a "dominant" solution, but how long did it take us to get there? By my count, a really long time! And along the way we've had to deal with all kinds of applications that just support the first and not the other. And it seems like far too many people still have just one foot in the door - take for instance the README files shipped with commercial game ports that advise using OSS at the first hint of trouble with Alsa.
A network device is way better abstracted by the operating system, so compatibility issues are of much smaller concern.
Quoted 1 line
Is this what we want for wireless?
We wouldn't get it, see above.
Hi!
Quoted 6 lines
Quoted 1 line
Like the OSS/Alsa or XFree3.x/XFree4.x situations.
And OSS/ALSA is an example why this is not a good thing:
- OSS in the kernel is unmaintained
- people forced to use OSS drivers can't use applications only supporting ALSA
Well, it is different. Current ieee80211 stack is going to be maintained by Intel -- because they need it for their hw. And it will be very easy to find maintainer for the new stack...
So we already have two-stack situation here.
Signature · 1 line
Thanks, Sharp!
Quoted 9 lines · Pavel Machek
Hi!
Quoted 6 lines
Quoted 1 line
Like the OSS/Alsa or XFree3.x/XFree4.x situations.
And OSS/ALSA is an example why this is not a good thing:
- OSS in the kernel is unmaintained
- people forced to use OSS drivers can't use applications only supporting ALSA
Quoted 5 lines
Well, it is different. Current ieee80211 stack is going to be maintained by Intel -- because they need it for their hw. And it will be very easy to find maintainer for the new stack...
So we already have two-stack situation here.
No, ieee80211 has always been intended for use by all drivers. Read the archives... there have been a few efforts to start merging HostAP and ieee80211 code, and further efforts exist out of tree that add softmac support.
Remember Linux's maxim: do what you must, and no more.
That implies that new users SHOULD update ieee80211 for their needs.
Jeff
Quoted 5 lines · Tim Tassonis
This is exactly the opposite of what Linus proposes in his management style document: "Avoid making decisions". At the moment, nobody seems to know what the "right" direction is, because the right direction is the one that will produce the better wireless support, and not the one that sounds better at the moment.
I won't try to speak for Linus (perhaps he'd like to pipe up at some point), but I think you're pulling that concept wayy out of context here.
Quoting ManagementStyle:
Quoted 5 lines
Btw, another way to avoid a decision is to plaintively just whine "can't we just do both?" and look pitiful. Trust me, it works. If it's not clear which approach is better, they'll eventually figure it out. The answer may end up being that both teams get so frustrated by the situation that they just give up.
Built into that paragraph, I think, is the assumption that you never 'do both'.
Also, referring to OSS/Alsa is just a great way to illustrate the problem with your idea. There is, today, finally a "dominant" solution, but how long did it take us to get there? By my count, a really long time! And along the way we've had to deal with all kinds of applications that just support the first and not the other. And it seems like far too many people still have just one foot in the door - take for instance the README files shipped with commercial game ports that advise using OSS at the first hint of trouble with Alsa.
Is this what we want for wireless?
Quoted 3 lines
Tim
Chase
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Adrian Bunk
Quoted 8 lines · Tim Tassonis
...
Quoted 3 lines
We can always undo mistakes later, but
we'll never get to that point if we don't start moving in one direction instead of ten.You were right if there were ten, but there seem to be only two at the moment. One stack will survive and one will die. There's no point in deciding this now.
Quoted 6 lines
No, we'll end up with two stacks, some drivers using the first stack and some the second one.
You can't simply let one stack die because this would imply either rewriting all drivers using this stack or dropping support for some hardware.
So, you don't want to remove OSS drivers anymore, I take it. Can't let bad stacks die!
-- Pete
Quoted 14 lines · Pete Zaitcev
Quoted 13 lines · Adrian Bunk
Quoted 8 lines · Tim Tassonis
...
Quoted 3 lines
We can always undo mistakes later, but
we'll never get to that point if we don't start moving in one direction instead of ten.You were right if there were ten, but there seem to be only two at the moment. One stack will survive and one will die. There's no point in deciding this now.
No, we'll end up with two stacks, some drivers using the first stack and some the second one.
Quoted 6 lines
Quoted 3 lines
You can't simply let one stack die because this would imply either rewriting all drivers using this stack or dropping support for some hardware.
So, you don't want to remove OSS drivers anymore, I take it. Can't let bad stacks die!
There are OSS drivers in the kernel that support hardware not supported by ALSA.
Quoted 1 line
-- Pete
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed