[petsc-dev] Using multiple mallocs with PETSc

Jed Brown jed at jedbrown.org
Tue Mar 14 16:04:06 CDT 2017


Barry Smith <bsmith at mcs.anl.gov> writes:

>> On Mar 14, 2017, at 3:23 PM, Jed Brown <jed at jedbrown.org> wrote:
>> 
>> Barry Smith <bsmith at mcs.anl.gov> writes:
>> 
>>>> On Mar 13, 2017, at 1:27 PM, Jed Brown <jed at jedbrown.org> wrote:
>>>> 
>>>> Satish Balay <balay at mcs.anl.gov> writes:
>>>>> stash the metadata for each allocation (and pointers for corresponding
>>>>> free) in a hash table for all mallocs that we need to track? [this
>>>>> avoids the wasted 'space' in each alloc.]
>>>> 
>>>> Sure, but this is just duplicating an implementation of malloc.
>>> 
>>>   No it isn't. It is a very thin wrapper around multiple current mallocs.
>> 
>> Meh, the proposal has more storage overhead than malloc().
>
>    It still doesn't even come close to providing the functionality of malloc, so isn't a duplication of malloc

Fine, it's more wasteful than malloc while doing less than malloc, and
still calls malloc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20170314/7c1569f2/attachment.sig>


More information about the petsc-dev mailing list