I have noticed that the kernel stack space in Linux is very small--
only 5300-odd bytes with the x86_64 kernel that I'm using right now.
I have run into problems with this, most notably with the deeply-
nested and recursive ACPI "driver" code. When I mentioned enlarging
the kernel stack on the
At 08:30 AM 3/24/2004 -0500, [EMAIL PROTECTED] wrote:
Ray/Chuck,
Thanks for all your help. Let me try a new approach, I have been vague on
the details because I thought my problem was very simple..here is a
detailed decryption of my problem...
I have developed a network driver for a custom fi
At 06:47 PM 3/24/2004 +0530, joy wrote:
Ray Olszewski wrote:
I haven't myself switched to the 2.6.x kernel series yet, but I have seen
reports warning of problems with some external add-in modules, including
the nvidia drivers ... showing up as high CPU loads caused, I think, by
context switchi
Ray/Chuck,
Thanks for all your help. Let me try a new approach, I have been vague on
the details because I thought my problem was very simple..here is a
detailed decryption of my problem...
I have developed a network driver for a custom fibre channel card. Though
the physical interface is F
Ray Olszewski wrote:
I haven't myself switched to the 2.6.x kernel series yet, but I have
seen reports warning of problems with some external add-in modules,
including the nvidia drivers ... showing up as high CPU loads caused,
I think, by context switching not being handled efficiently. (Also
pa3gcu wrote:
I dont want to sound like a wet blanket, however i have a machine here running
a 2.6 kernel, be aware there are issues with the nvidia video drivers, or at
least i have some.
I too had some problems in the beginning, but I believe APIC support on
uniprocessor systems breaks the
