Re: [E-devel] eina mempool review and descriptions?
On Thu, 21 Jan 2010, Gustavo Sverzut Barbieri wrote: Hey all, I'm doing ebuilds for gentoo and I want to make them use configurable mempools, however the names are stupidly bad and I have no idea the use so I enable or disable them. could someone (ie: cedric) document what are these, how they are chosen, which should be really enabled and which could be left out since are experiments? added in the mempool doc. Feel free to fix spelling and grammar :-) Vncent -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] eina mempool review and descriptions?
On Fri, Jan 22, 2010 at 11:14 AM, Cedric BAIL moa.blueb...@gmail.com wrote: On Thu, Jan 21, 2010 at 11:13 PM, Gustavo Sverzut Barbieri barbi...@profusion.mobi wrote: I'm doing ebuilds for gentoo and I want to make them use configurable mempools, however the names are stupidly bad and I have no idea the use so I enable or disable them. could someone (ie: cedric) document what are these, how they are chosen, which should be really enabled and which could be left out since are experiments? So we have : * buddy: Last one, from turran, I will let him describe this one. The buddy mempool uses the buddy allocator algorithm (http://en.wikipedia.org/wiki/Buddy_memory_allocation ), but the eina's implementation differs in the sense that the chunk information is not stored on the chunk itself but on another memory area. This is useful for cases where the memory to manage might be slower to access or limited (like video memory) * chained_pool: The default one, basically do big malloc and split the result in chunk of the required size that are pushed inside a stack. Then when requested it take this pointer from the stack to give them to whoever whant them. * ememoa_fixed and ememoa_unknown: Are experimental allocator, could be usefull when you have a fixed amount of memory. * fixed_bitmap: This one, malloc 32 * the required size and push the pool pointer in a rbtree. To find empty space in a pool, it will just search for the first bit set in a int (32bits). And when a pointer is freed, it will do a search inside the rbtree. * pass_through: This one just call malloc and free. It may be faster on some computer than using our own allocator (typical case when you have huge L2 cache, over 4MB). Yeah, I know, better docs required and perhaps add some benchmark result too. -- Cedric BAIL -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] eina mempool review and descriptions?
On Thu, Jan 21, 2010 at 11:13 PM, Gustavo Sverzut Barbieri barbi...@profusion.mobi wrote: I'm doing ebuilds for gentoo and I want to make them use configurable mempools, however the names are stupidly bad and I have no idea the use so I enable or disable them. could someone (ie: cedric) document what are these, how they are chosen, which should be really enabled and which could be left out since are experiments? So we have : * buddy: Last one, from turran, I will let him describe this one. * chained_pool: The default one, basically do big malloc and split the result in chunk of the required size that are pushed inside a stack. Then when requested it take this pointer from the stack to give them to whoever whant them. * ememoa_fixed and ememoa_unknown: Are experimental allocator, could be usefull when you have a fixed amount of memory. * fixed_bitmap: This one, malloc 32 * the required size and push the pool pointer in a rbtree. To find empty space in a pool, it will just search for the first bit set in a int (32bits). And when a pointer is freed, it will do a search inside the rbtree. * pass_through: This one just call malloc and free. It may be faster on some computer than using our own allocator (typical case when you have huge L2 cache, over 4MB). Yeah, I know, better docs required and perhaps add some benchmark result too. -- Cedric BAIL -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] eina mempool review and descriptions?
On Fri, 22 Jan 2010, Cedric BAIL wrote: On Thu, Jan 21, 2010 at 11:13 PM, Gustavo Sverzut Barbieri barbi...@profusion.mobi wrote: I'm doing ebuilds for gentoo and I want to make them use configurable mempools, however the names are stupidly bad and I have no idea the use so I enable or disable them. could someone (ie: cedric) document what are these, how they are chosen, which should be really enabled and which could be left out since are experiments? So we have : * buddy: Last one, from turran, I will let him describe this one. * chained_pool: The default one, basically do big malloc and split the result in chunk of the required size that are pushed inside a stack. Then when requested it take this pointer from the stack to give them to whoever whant them. * ememoa_fixed and ememoa_unknown: Are experimental allocator, could be usefull when you have a fixed amount of memory. * fixed_bitmap: This one, malloc 32 * the required size and push the pool pointer in a rbtree. To find empty space in a pool, it will just search for the first bit set in a int (32bits). And when a pointer is freed, it will do a search inside the rbtree. * pass_through: This one just call malloc and free. It may be faster on some computer than using our own allocator (typical case when you have huge L2 cache, over 4MB). Yeah, I know, better docs required and perhaps add some benchmark result too. I'll add those description in eina doxy doc this evening Vincent -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] eina mempool review and descriptions?
Hey all, I'm doing ebuilds for gentoo and I want to make them use configurable mempools, however the names are stupidly bad and I have no idea the use so I enable or disable them. could someone (ie: cedric) document what are these, how they are chosen, which should be really enabled and which could be left out since are experiments? BR, -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
