Re: C++ Memory Management Innovation: GC Allocator

On 4ÔÂ22ÈÕ, ÉÏÎç9ʱ52·Ö, "Chris Thomasson" <cris...@[EMAIL PROTECTED]
> wrote:
> "Chris Thomasson" <cris...@[EMAIL PROTECTED]
> wrote in message
>
> If I am correct, well, "perhaps" I have something that just might be
able to
> help your allocator. There is an invention that can transform most
> single-threaded memory allocators into scaleable multi-threaded ones;
here
> is my initial post:
>
> http://groups.google.com/group/comp.arch/browse_frm/thread/6dc825ec99...
>
> basically, you create single-threaded allocator and plug it into the
system,
> then, boom, its multi-threaded. If you have any questions, feel free to
fire
> away...


I'm sorry but I think you misunderstand my points. I don't want to
create single-threaded allocator.

Why? Sharing GC Allocator in multi threads is not recommended. It
means that sharing memory between threads is also not recommended. If
you REALLY want to share memory, use new/delete or anything else.

For users of GC Allocator, we suggest that only use ONE BlockPool
instance in ONE thread, and ONE thread may use multiple PRIVATE
"ScopeAlloc" instances (depend on your requirement) to allocate
memory.

Lance Diduck is right:

Use non-static allocator instances to allocate memory instead of
global new/delete procedures. Then multithreads locks are OPTIONAL and
you can use explicit locks if you need.


-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]