Hello All.

 

I meet the performance problem about madvise() function in DFB1.0.0

This function consumes the 50ms time in my target device.

In my previous target device, it takes just 1ms.

This function is called many times when application is running.

So I MUST remove this function if I can't resolve this problem in kernel
side.

 

I'd like to know it is O.K although I remove this function.

In DirectFB 1.3, this function seems to be optional.

That is, if set the 'madv-remove' in config file, madvise() functions is not
called.

 

This function is defined in \lib\fusion\shm\heap.c:_fusion_shfree() in
DFB1.0.0

 

/* FIXME: as this is used when kernel is detected as >= 2.6.19.2 only, this
fallback definition should be ok for now */

#ifndef MADV_REMOVE

#define MADV_REMOVE 9

#endif

               /* Punch a hole into the tmpfs file to really free RAM. */

               if (fusion_config->madv_remove)

                    madvise( ADDRESS(block), blocks * BLOCKSIZE, MADV_REMOVE
);

 

 

 

 

=================================

Inpyo Kang

Linux Lab, Open OS S/W Group

Mobile R&D, Samsung Electronics

--------------------------------

Office : +82-31-301-7675

H.P    : +82-10-7260-8850

E-mail :  <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]

=================================

 

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

Reply via email to