o yes, in 1.0.x that's not an option, you're right.
ok.. kernel 2.6.25 is good enough, should work... strange.

for madvise, my understanding is the following.
if fusion uses memory, it does not use malloc. That would be pointless, 
since fusion requires shared memory. Instead, it simply does a "mmap" of 
"/dev/shm" by default, and uses this to do it's own heap management.
At first, the area mapped by mmap is not paged in. This happens of 
course only when you "malloc" an area from fusion. After a while, you 
can expect to see holes in this area. Problem is that until 2.6.19 
kernel, there was no (stable) way to 'release' those holes, i.e. page 
out. For Linux, they were still 'occupied'. This is what madvice( x, 
MADV_REMOVE ) does; it clears the "paging" flags so the area can be 
paged out.
Concluding, if you do not have enough memory, and if you don't page to 
flash/disk, and if you "fusion " alloc/release a lot with undetermined 
and changing request sizes, you might run into low memory.

Greets
Niels

Inpyo Kang wrote:
> My kernel version is 2.6.25 and I use the DirectFB1.0.0.
> In DirectFB1.0.0, I can't configure the 'no-madv-remove' in directfbrc.
> So, I commented out below code such as,
> ----------------------------------------------------------------------------
> if (fusion_config->madv_remove)
> //  madvise( ADDRESS(block), blocks * BLOCKSIZE, MADV_REMOVE );
>
> Would you explain more detail about this function?
> 1. The reason why this function is added in DirectFB source
> 2. The functionality of this function. I found out this function's manual in
> web but I don't understand this function exactly because of lack of kernel
> experience.
> 3. Is there any side effect if I remove this function?
>     My question is not how to remove this function in terms of DirectFB.
>     I am eager to know there is no side effect in my system when removing
> this function.
>
>   

-- 

.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/                 |
"------------------------------------------" 

_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to