On Mar 31, 2009, at 2:59 AM, Rainer Jung wrote:
On 30.03.2009 20:58, Jeff Trawick wrote:
On Mon, Mar 30, 2009 at 2:33 PM, Jeff Trawick mailto:traw...@gmail.com>> wrote:
On Mon, Mar 30, 2009 at 2:07 PM, Jim Jagielski mailto:j...@jagunet.com>> wrote:
Anyone know if:
# POSIX semaphores and c
On 04/03/2009 06:12 PM, Mladen Turk wrote:
> Ruediger Pluem wrote:
>>
>> On 04/03/2009 04:31 PM, mt...@apache.org wrote:
>>> Author: mturk
>>> Date: Fri Apr 3 14:31:16 2009
>>> New Revision: 761692
>>>
>>> URL: http://svn.apache.org/viewvc?rev=761692&view=rev
>>> Log:
>>> Make final_block dynamic
Ruediger Pluem wrote:
>
> On 04/03/2009 04:31 PM, mt...@apache.org wrote:
>> Author: mturk
>> Date: Fri Apr 3 14:31:16 2009
>> New Revision: 761692
>>
>> URL: http://svn.apache.org/viewvc?rev=761692&view=rev
>> Log:
>> Make final_block dynamic.
>> It is used only so we can create our mutex that w
On 04/03/2009 04:31 PM, mt...@apache.org wrote:
> Author: mturk
> Date: Fri Apr 3 14:31:16 2009
> New Revision: 761692
>
> URL: http://svn.apache.org/viewvc?rev=761692&view=rev
> Log:
> Make final_block dynamic.
> It is used only so we can create our mutex that will survive pool_clear
Why? The
URL: http://svn.apache.org/viewvc?rev=761692&view=rev
Log:
Make final_block dynamic.
It is used only so we can create our mutex that will survive pool_clear
No mater what you do the new implementation simply sucks
when compared to the old one.
The performance is 2 to 20+ times! slower dependin
rpl...@apache.org wrote:
Author: rpluem
Date: Fri Apr 3 13:13:26 2009
New Revision: 761662
URL: http://svn.apache.org/viewvc?rev=761662&view=rev
Log:
* Correctly setup size field for the final_blocks field.
Modified:
apr/apr/trunk/memory/unix/apr_pools.c
Modified: apr/apr/trunk/memory/uni
