Severe trashing in 2.4.4
Quoted 4 lines · Alexander Viro
Quoted 3 lines
Hmm... I'd say that you also have a leak in kmalloc()'ed stuff - something in 1K--2K range. From your logs it looks like the thing never shrinks and grows prettu fast...
You could enable STATS in mm/slab.c, then the number of alloc and free calls would be printed in /proc/slabinfo.
Quoted 1 line
Yeah, those as well. I kinda guessed they were related...
Could you check /proc/sys/net/core/hot_list_length and skb_head_pool (not available in /proc, use gdb --core /proc/kcore)? I doubt that this causes your problems, but the skb_head code uses a special per-cpu linked list for even faster allocations.
Which network card do you use? Perhaps a bug in the zero-copy code of the driver?
--
Manfred
Quoted 5 lines · Manfred Spraul
You could enable STATS in
mm/slab.c, then the number of alloc and free calls would be printed in/proc/slabinfo.Quoted 1 line
Yeah, those as well. I kinda guessed they were related...
Quoted 7 lines
Could you check
/proc/sys/net/core/hot_list_lengthandskb_head_pool(not available in /proc, use gdb --core/proc/kcore)? I doubt that this causes your problems, but theskb_headcode uses a special per-cpu linked list for even faster allocations.Which network card do you use? Perhaps a bug in the zero-copy code of the driver?
I'll give it a go once I reboot into 2.4.4 again (now in 2.4.3 to get some 'work' done). Using the dreaded ne2k cards (two of them), which have caused me more than one headache already...
I'll have a look at the driver for these cards.
Cheers//Frank
Signature · 9 lines
WWWWW _______________________
## o o\ / Frank de Lange \
}# \| / \
##---# _/ <Hacker for Hire> \
#### \ +31-320-252965 /
\ [email protected] /
-------------------------
[ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est." ]