<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 09/19/2014 07:49 PM, Nathaniel
McCallum wrote:<br>
</div>
<blockquote cite="mid:1411148975.18665.5.camel@redhat.com"
type="cite">
<pre wrap="">This is an optimization from patch 0062 (rescinded) which I think is
worth keeping. There is no ticket for this.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Freeipa-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Freeipa-devel@redhat.com">Freeipa-devel@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/freeipa-devel">https://www.redhat.com/mailman/listinfo/freeipa-devel</a></pre>
</blockquote>
<font face="Times New Roman, Times, serif">Hello,<br>
<br>
</font>
<blockquote><font face="Times New Roman, Times, serif">That is exact
that slapi* are doing a intensive usage of the of alloc/free.
Using a stack allocated mods would reduce the number of
alloc/free but I afraid it will not have a significant impact.
For example further slapi_modify_internal is doing tons of
alloc/free.<br>
<br>
Also I think it is not possible to use stack allocated mods. In
fact mods will be modified by internal_mod (for example to add
'modifytimestamp', 'modifiersname') and mods will be
reallocated. This could also occurs from plugins.<br>
Finally if a modify retry occurs, the original mods are freeed.<br>
<br>
thanks<br>
thierry<br>
</font></blockquote>
</body>
</html>