[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: Memory usage when opening Linux Kernel in KDevelop
From: David Nolden <zwabel () googlemail ! com>
Date: 2010-11-20 22:33:57
Message-ID: AANLkTimm2e1oh=vjK=tboEBSa=aO1AtcQKcSrM-aS=at () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I don't remember anything about rxx::allocator, i guess its just the default
for C++.
About monster buckets: Normally a bucket has a size of 64kb, but when an
item is allocated that is larger than that, a "monster bucket" is allocated,
which spans the space of multiple buckets.
Am 20.11.2010 19:50 schrieb "Milian Wolff" <mail@milianw.de>:
On Saturday 20 November 2010 18:01:37 David Nolden wrote:
> Buckets are the memory-units that are us...
Ok, so it's expected - thanks for clarifiying that. Can you also answer my
other questions, then I'll add some ApiDox to document that for the future.
> Anyway, the linux kernel is HUGE, so I don't see an immediate need for
> action here.
Optimization is always good but you are right in the sense that it works
quite
well already as I said.
Bye
--
Milian Wolff
mail@milianw.de
http://milianw.de
--
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[Attachment #5 (text/html)]
<p>I don't remember anything about rxx::allocator, i guess its just the default \
for C++.</p> <p>About monster buckets: Normally a bucket has a size of 64kb, but when \
an item is allocated that is larger than that, a "monster bucket" is \
allocated, which spans the space of multiple buckets.</p> <p><blockquote \
type="cite">Am 20.11.2010 19:50 schrieb "Milian Wolff" <<a \
href="mailto:mail@milianw.de">mail@milianw.de</a>>:<br><br><p><font \
color="#500050">On Saturday 20 November 2010 18:01:37 David Nolden wrote:<br> > \
Buckets are the memory-units that are us...</font></p>Ok, so it's expected - \
thanks for clarifiying that. Can you also answer my<br> other questions, then \
I'll add some ApiDox to document that for the future.<br> <p><font \
color="#500050"><br>> Anyway, the linux kernel is HUGE, so I don't see an \
immediate need for<br>> action here.<br></font></p>Optimization is always good but \
you are right in the sense that it works quite<br>
well already as I said.<br>
<br>
Bye<br>
<font color="#888888">--<br>
Milian Wolff<br>
<a href="mailto:mail@milianw.de">mail@milianw.de</a><br>
<a href="http://milianw.de" target="_blank">http://milianw.de</a><br>
</font><br>--<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" \
target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
<br></blockquote></p>
--
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic