[ATrpms-devel] Re: nvidia-graphics 6106
stesmi at stesmi.com
Tue Aug 3 22:57:25 CEST 2004
>>It's kernel memory. I bet that instead of using the stack they
>>threw variables globally and now they're eating kernel memory which
>>is limited on any setup and has nothing to do with normal memory.
>>That is, when nvidia made the drivers 4k compatible. They have
>>to put the data SOMEWHERE after all.
>>The memory will be non-swappable and is limited to (I believe) 128KiB,
>>at least on i386. If things have changed since I last looked at the
>>limits I don't know but that's what it was back then.
> While I have no RH9 box anymore to test this on, shouldn't the same
> happen to FC1 and FC2? FC1 and FC2 are happily working with 6106,
> with both 4kstacks or 8kstacks.
But it IS working for him isn't it ? I thought it was only that
he can't load more than one module and I can't remember what it was,
but that module he's loading is trying to allocate 29k of kernel
memory. That's one fourth of all available memory that's available
to all modules.
What I'm saying is that it's the combination of modules and not
any particular module's fault. Reproducing his pattern of module
usage with any other kernel and/or distro should yield the same
result as long as the modules use more or less the same amount
of kernel memory.
More information about the atrpms-devel