Date: Mon, 2 Dec 2013 12:36:11 +0000 (UTC) From: jb <jb.1234abcd@gmail.com> To: freebsd-current@freebsd.org Subject: Re: [RFC] how to get the size of a malloc(9) block ? Message-ID: <loom.20131202T132813-715@post.gmane.org> References: <CA%2BhQ2%2BgK1pc_aS1LEKp29Bi=MHFtJCkw2uOrib_9wQ-7AziH=w@mail.gmail.com> <loom.20131130T002152-608@post.gmane.org> <CA%2BhQ2%2Bj0cYW0dfhEtMGRXWhXhS=VF_N_ZB=JmcqRUofFKWXFiQ@mail.gmail.com> <loom.20131130T012034-966@post.gmane.org> <CA%2BhQ2%2BiCjnxUMP0v6d5ez=n07MBT5hLXzoa%2B1wTff3Wrtm=SHQ@mail.gmail.com> <52995C15.7010903@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<dt71 <at> gmx.com> writes:
>
> So new flags could be [1]:
> - realloc_flags(p, s, REALLOCF_NO_MOVE)
> ...
> - realloc_flags(p, s, REALLOCF_NO_MOVE | REALLOCF_ELASTIC)
> ...
> For this, there could be a REALLOCF_FORCE flag
In case of realloc_flags() failing the request, to avoid unnecessary
followups with regular realloc() when desired, we should include an option
like REALLOCF_FALLBACK_ANY that would allow to fallback on the regular
realloc() logic, in one call.
In addition, because I have an impression that realloc_flags() may have
a future as a replacement for regular realloc() and we should aim for it,
we should include an option like REALLOCF_ANY for that purpose.
So far, the options could be as follows:
- realloc_flags(p, s, option)
where option is one or a combination (where appropriate) of:
REALLOCF_ANY - default (move or no-move; regular realloc())
REALLOCF_NO_MOVE - no-move
REALLOCF_ELASTIC - combined with REALLOCF_NO_MOVE
REALLOCF_FORCE - combined with REALLOCF_NO_MOVE
REALLOCF_FALLBACK_ANY - combined with REALLOCF_NO_MOVE or its
derivatives like REALLOCF_ELASTIC, etc
jb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?loom.20131202T132813-715>