Memory usage when opening Linux Kernel in KDevelop

Milian Wolff mail at milianw.de
Mon Nov 22 12:09:03 UTC 2010


On Sunday 21 November 2010 20:03:53 Christoph Bartoschek wrote:
> Am Sonntag 21 November 2010 schrieb Christoph Cullmann:
> > On Sunday 21 November 2010 00:02:13 Milian Wolff wrote:
> > >   On Saturday 20 November 2010 23:33:57 David Nolden wrote:
> > > > I don't remember anything about rxx::allocator, i guess its just the
> > > > default for C++.
> > > 
> > > For the cpplang plugin? But the question is *why*, really - to me it
> > > looks like one of Robertos "I write my own allocator" - "Why?" -
> > > "Because I can!"  moments... I'll send him a mail asking him for the
> > > reasons.
> 
> Does it store the size of the allocated chunks? It is better to not store
> it. This can save some memory.

You'll have to study the sources for yourself.

And I've got a reply from Roberto, the allocator is used in the mem pool for 
the AST among other things, so it's perfectly fine (compare to e.g. kdev-pg-
allocator.h).

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20101122/72b58910/attachment.sig>


More information about the KDevelop-devel mailing list