Bigphysarea and mbuff

Hi guys,

For some reason I can't get mbuffs to work in the same kernel 
module as bigphysareas!

I have a 1GB system, reserve 200MB as bigphysarea at boot, then allocate
this memory using bigphysarea_alloc() and give it to TLSF so that I can 
have dynamic memory in an rt-thread.  That part works OK.

*However* when I create an mbuff to share with userspace (has nothing to 
do with the bigphysarea per se), userspace sees garbage in the mbuff. 
Kernel space continues to see valid data in the mbuff.

I suspect either TLSF is corrupting memory or that bigphysarea itself is 
broken.  Does anyone know if TLSF can be compiled with MAX_FLI of 31 (to 
support up to 2048MB memory)?


The weird thing is that if I disable bigphysarea and instead give TLSF a 
region allocated with vmalloc() everything works fine... so it might not 
be TLSF's fault, but rather the fact that I have a bigphysarea and an 
mbuff both in the same address space.

It's a really weird bug.

I'm on 2.4.29-rtl3.2 patched for bigphysarea.

Any thoughts?  Is bigphysarea known to not work so well with the mbuff 
device?

Anyone else get both bigphysarea and mbuffs working?

-Calin

_______________________________________________
Rtl mailing list
[email protected]
http://hq.fsmlabs.com/mailman/listinfo/rtl
http:/www.rtlinux-gpl.org/