i386: always use 4k stacks
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 1 line · Jeff V. Merkey
Why does the kernel need to be limited to 4K? for kernel preemption?
No, because it makes a whole lot of things simpler and more reliable if the kernel stack is only one page.
Quoted 2 lines
Someone needs to fix this. It's busted. It makes porting code between Windows and Linux and other OS's difficult to support.
Ease of porting drivers written for other OSes to Linux is clearly not a high priority for the kernel community..
Signature · 3 lines
Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [email protected] Home Page: http://www.roberthancock.com/
Quoted 5 lines · Robert Hancock
Quoted 1 line · Jeff V. Merkey
Why does the kernel need to be limited to 4K? for kernel preemption?
Quoted 7 lines
No, because it makes a whole lot of things simpler and more reliable if the kernel stack is only one page.
Quoted 2 lines
Someone needs to fix this. It's busted. It makes porting code between Windows and Linux and other OS's difficult to support.
Ease of porting drivers written for other OSes to Linux is clearly not a high priority for the kernel community..
What? There's more kernel apps than just ndis network drivers that get ported. ndiswrapper is busted (which is used for a lot of laptops) without 4K stacks. My laptop is a Compaq and there isn't a Linux driver for the wireless. I also discovered Fedora Core 4 won't install on a Compaq Presario with SATA (stacks crashes).
What are you saying? People with wireless and laptops who run Linux can't because ndiswrapper is busted without 8K stacks?
Should be a configurable option 4-16K -- set at RUN TIME on the COMMAND LINE of the BOOT LOADER. Peopl can set
profile=? why not kernel default stack size. That way Fedora, ES, AS, and Suse can run out of the box on laptops like Windows,
or is M$ going to keep owning the desktop?
Jeff
Quoted 2 lines · Jeff V. Merkey
What? There's more kernel apps than just ndis network drivers that get ported. ndiswrapper is busted (which is used for a lot of laptops) without 4K stacks.
Which is why ndiswrapper needs to get fixed to work with 4K stacks. ndiswrapper is the thing that's doing the wierd stuff, it needs to adapt to the kernel, not the other way around. The reasons to use 4K stacks are strong enough that they are not made up for by the fact that ndiswrapper currently would like to have more stack space.
Windows apparently has 12K of kernel stack for drivers.. in that case even 8K of stack in Linux would not necessarily be enough. If ndiswrapper wants to run Windows code in the kernel with any amount of reliability it should be providing its own stack which is the size that the code expects.
Quoted 2 lines
My laptop is a Compaq and there isn't a Linux driver for the wireless. I also discovered Fedora Core 4 won't install on a Compaq Presario with SATA (stacks crashes).
How do you know this is related to the stack? Did you report this as a bug?
Signature · 3 lines
Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [email protected] Home Page: http://www.roberthancock.com/
Quoted 7 lines · Robert Hancock
Quoted 2 lines · Jeff V. Merkey
What? There's more kernel apps than just ndis network drivers that get ported. ndiswrapper is busted (which is used for a lot of laptops) without 4K stacks.
Which is why ndiswrapper needs to get fixed to work with 4K stacks. ndiswrapper is the thing that's doing the wierd stuff, it needs to adapt to the kernel, not the other way around. The reasons to use 4K stacks are strong enough that they are not made up for by the fact that ndiswrapper currently would like to have more stack space.
The NDIS drivers require the 8K stack, not ndiswrapper.
Quoted 8 lines
Windows apparently has 12K of kernel stack for drivers.. in that case even 8K of stack in Linux would not necessarily be enough. If ndiswrapper wants to run Windows code in the kernel with any amount of reliability it should be providing its own stack which is the size that the code expects.
Quoted 2 lines
My laptop is a Compaq and there isn't a Linux driver for the wireless. I also discovered Fedora Core 4 won't install on a Compaq Presario with SATA (stacks crashes).
How do you know this is related to the stack? Did you report this as a bug?
Because I use MDB, a kernel debugger I wrote that inserts beneath Linux via DRLX or inside of it, and I watched it crash in the Linux SCSI code. There's code in Linux proper that also walks off the end of the stack. No I did not report it. But now I have.
Jeff
Quoted 10 lines · Robert Hancock
Quoted 3 lines · Jeff V. Merkey
What? There's more kernel apps than just ndis network drivers that get ported. ndiswrapper is busted (which is used for a lot of laptops) without 4K stacks.
Which is why ndiswrapper needs to get fixed to work with 4K stacks. ndiswrapper is the thing that's doing the wierd stuff, it needs to adapt to the kernel, not the other way around. The reasons to use 4K stacks are strong enough that they are not made up for by the fact that ndiswrapper currently would like to have more stack space.
There was a discussion weeks (or already months?) ago about this. The ndiswrapper maintainer had no problem with private stacks for the NDIS drivers but IIRC there where some issues with callbacks from the NDIS drivers which led to the conclusion that it's way too much of a hassle to get it working and stable.
And yes, you need ndiswrapper for almost all of the WLAN drivers since there is no documentation of them.
Bernd
Signature · 3 lines
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and ServicesQuoted 3 lines
And yes, you need ndiswrapper for almost all of the WLAN drivers since there is no documentation of them.
you're wrong.
documentation for broadcom wireless:
http://bcm-specs.sipsolutions.net/
embrionic driver based on this spec:
http://bcm43xx.berlios.de/
driver for atheros wireless is nearly done:
http://www.selenic.com/pipermail/kernel-mentors/2005-August/000351.html
now if people started to help these folks instead of crying for ndiswrapper binary solutions maybe those drivers will be finished quicker.
Quoted 4 lines · Arjan van de Ven
documentation for broadcom wireless:
http://bcm-specs.sipsolutions.net/
embrionic driver based on this spec:
http://bcm43xx.berlios.de/
Thanks, someone mentioned this but didn't provide any links...
Quoted 3 lines
now if people started to help these folks instead of crying for ndiswrapper binary solutions maybe those drivers will be finished quicker.
Indeed, time to dig out my Linksys WPC54G.
-cp
Signature · 1 line
Phishing, pharming; n.: Ways to obtain phood. -- The Devil's Infosec Dictionary
Quoted 13 lines · Arjan van de Ven
Quoted 4 lines
And yes, you need ndiswrapper for almost all of the WLAN drivers since there is no documentation of them.
you're wrong.
documentation for broadcom wireless:
http://bcm-specs.sipsolutions.net/
embrionic driver based on this spec:
http://bcm43xx.berlios.de/
Quoted 9 lines
driver for atheros wireless is nearly done:
http://www.selenic.com/pipermail/kernel-mentors/2005-August/000351.htmlnow if people started to help these folks instead of crying for ndiswrapper binary solutions maybe those drivers will be finished quicker.
No one is crying about ndiswrapper, some folks just want to use Linux on their laptops without waiting
two years for all the drivers to port to Linux. Make the 4K stack setting a command line option. Problem solved.
Jeff
Quoted 8 lines
-
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/
JVM> No one is crying about ndiswrapper, some folks just want to use Linux on JVM> their laptops without waiting
JVM> two years for all the drivers to port to Linux. Make the 4K stack
JVM> setting a command line option. Problem solved.
Just do a "fgrep -rI CONFIG_4KSTACKS linux" and see that this is just not a matter of one malloc call but the code differs in many things. That's what gives 4KSTACKS its strength.
Signature · 1 line
Meelis Roos
Quoted 19 lines · Jeff V. Merkey
Quoted 6 lines · Robert Hancock
Quoted 1 line · Jeff V. Merkey
Why does the kernel need to be limited to 4K? for kernel preemption?
Quoted 8 lines
No, because it makes a whole lot of things simpler and more reliable if the kernel stack is only one page.
Quoted 2 lines
Someone needs to fix this. It's busted. It makes porting code between Windows and Linux and other OS's difficult to support.
Ease of porting drivers written for other OSes to Linux is clearly not a high priority for the kernel community..
Quoted 8 lines
What? There's more kernel apps than just ndis network drivers that get ported. ndiswrapper is busted (which is used for a lot of laptops) without 4K stacks. My laptop is a Compaq and there isn't a Linux driver for the wireless. I also discovered Fedora Core 4 won't install on a Compaq Presario with SATA (stacks crashes).
What are you saying? People with wireless and laptops who run Linux can't because ndiswrapper is busted without 8K stacks?Should be a configurable option 4-16K -- set at RUN TIME on the COMMAND LINE of the BOOT LOADER. Peopl can set
profile=? why not kernel default stack size. That way Fedora, ES, AS, and Suse can run out of the box on laptops like Windows,
or is M$ going to keep owning the desktop?
Having stack size as a compile time value and having it as a runtime value are two totally different problems. I just don't see much benefit from making changing the size easy, when it is likely to be a VERY infrequent need at all.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 1 line · Denis Vlasenko
On Wednesday 16 November 2005 00:27, Giridhar Pemmasani wrote:
[because of ndiswrapper, ...]
Quoted 2 lines
Companies got nice excuse for not giving us docs, making those months/years even longer.
<snip>
Quoted 3 lines
Ok, how can we make any progress on obtaining docs for TI acx wireless chipset? Or on Prism54 "softmac" chipset? The reply is "Open source driver already exists (ndiswrapper), go away".
That why are these cards (Netgear WG511) are documented as being supported in the CONFIG_PRISM54 help text. I asume the list was copied from the same bad list of supported cards that made me buy one in the first place. If there was no ndiswrapper support, I'd have been fooled to completely waste my money, with ndiswrapper I can at least partially use it. I do neither want to wait some years to use a by-then obsolete card nor can I help developing a driver beyond doing some testing.
BTW: What about creating a "Native linux support" logo saying "If you find a slot and plug it in, you can use it with a vanilla kernel on any arch and get vendor support"? That would help against Netgear's faksimile products of working models or ATI's claims for having "linux support".
Signature · 2 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF verbreiteten Lügen zu sabotieren.
Quoted 4 lines · Bodo Eggert
BTW: What about creating a "Native linux support" logo saying "If you find a slot and plug it in, you can use it with a vanilla kernel on any arch and get vendor support"? That would help against Netgear's faksimile products of working models or ATI's claims for having "linux support".
We can do that. Well, Linus can do that... he holds the trademark, he could create a "Linux native driver" emblem. Have to be a tad careful to require open source to get it, but I don't know about requiring GPL. In the real world a single FOSS driver which could be used for Linux, BSD, and Solaris would be easier for a vendor to justify, but it would have to be covered by a license which satisfied all applications.
Even if it couldn't be part of a kernel.org source, at least if it were available in source it would satisfy better than ndis. Anyone with real expertise in what license could apply to all kernels please speak up.
None of this should imply that I have changed my mind about larger stack sizes being desirable.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me