Re: [sqlite] mem5 ("buddy system") usable?
On Apr 1, 2008, at 2:37 PM, Richard Klein wrote: >> > Fair enough. But can I assume that mem5 *does* currently > work, as far as you know? (I'd really like to use it, as > I'm using SQLite on an embedded system.) > mem5 works as far as I know. D. Richard Hipp [EMAIL PROTECTED] ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] mem5 ("buddy system") usable?
> On Mar 31, 2008, at 10:00 PM, Richard Klein wrote: >> I just downloaded 3.5.7, and noticed that there is a >> new memory allocator mem5.c, which apparently uses the >> "buddy system" to allocate power-of-two-sized chunks >> of memory from a static pool. This allocator is used >> by defining SQLITE_POW2_MEMORY_SIZE. >> >> Is it okay to use this allocator, or is it only exper- >> imental (and therefore liable to disappear in a future >> release)? >> > > I'm not making any promises about any of the current five > memory allocators. I might decide to replace them all tomorrow. > > But mem5 is high on the list of memory allocators to keep > since it can, under some circumstances, guarantee not to > fragment memory, which is a desirable property for > embedded systems. > > D. Richard Hipp > [EMAIL PROTECTED] > Fair enough. But can I assume that mem5 *does* currently work, as far as you know? (I'd really like to use it, as I'm using SQLite on an embedded system.) - Richard Klein ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] mem5 ("buddy system") usable?
On Mar 31, 2008, at 10:00 PM, Richard Klein wrote: > I just downloaded 3.5.7, and noticed that there is a > new memory allocator mem5.c, which apparently uses the > "buddy system" to allocate power-of-two-sized chunks > of memory from a static pool. This allocator is used > by defining SQLITE_POW2_MEMORY_SIZE. > > Is it okay to use this allocator, or is it only exper- > imental (and therefore liable to disappear in a future > release)? > I'm not making any promises about any of the current five memory allocators. I might decide to replace them all tomorrow. But mem5 is high on the list of memory allocators to keep since it can, under some circumstances, guarantee not to fragment memory, which is a desirable property for embedded systems. D. Richard Hipp [EMAIL PROTECTED] ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] mem5 ("buddy system") usable?
I just downloaded 3.5.7, and noticed that there is a new memory allocator mem5.c, which apparently uses the "buddy system" to allocate power-of-two-sized chunks of memory from a static pool. This allocator is used by defining SQLITE_POW2_MEMORY_SIZE. Is it okay to use this allocator, or is it only exper- imental (and therefore liable to disappear in a future release)? Thanks, - Richard Klein ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
