From owner-freebsd-current@FreeBSD.ORG  Thu Dec  5 21:30:15 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4F3ED907
 for <freebsd-current@freebsd.org>; Thu,  5 Dec 2013 21:30:15 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 066581DB6
 for <freebsd-current@freebsd.org>; Thu,  5 Dec 2013 21:30:14 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <freebsd-current@m.gmane.org>) id 1VogUl-0006c0-Tq
 for freebsd-current@freebsd.org; Thu, 05 Dec 2013 22:30:06 +0100
Received: from 79-139-19-75.prenet.pl ([79.139.19.75])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <freebsd-current@freebsd.org>; Thu, 05 Dec 2013 22:30:03 +0100
Received: from jb.1234abcd by 79-139-19-75.prenet.pl with local (Gmexim 0.1
 (Debian)) id 1AlnuQ-0007hv-00
 for <freebsd-current@freebsd.org>; Thu, 05 Dec 2013 22:30:03 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-current@freebsd.org
From: jb <jb.1234abcd@gmail.com>
Subject: Re: [RFC] how to get the size of a malloc(9) block ?
Date: Thu, 5 Dec 2013 21:29:41 +0000 (UTC)
Lines: 22
Message-ID: <loom.20131205T221554-758@post.gmane.org>
References: <CA+hQ2+gK1pc_aS1LEKp29Bi=MHFtJCkw2uOrib_9wQ-7AziH=w@mail.gmail.com>
 <loom.20131130T002152-608@post.gmane.org>
 <CA+hQ2+j0cYW0dfhEtMGRXWhXhS=VF_N_ZB=JmcqRUofFKWXFiQ@mail.gmail.com>
 <loom.20131130T012034-966@post.gmane.org>
 <CA+hQ2+iCjnxUMP0v6d5ez=n07MBT5hLXzoa+1wTff3Wrtm=SHQ@mail.gmail.com>
 <52995C15.7010903@gmx.com> <loom.20131202T132813-715@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: sea.gmane.org
User-Agent: Loom/3.14 (http://gmane.org/)
X-Loom-IP: 79.139.19.75 (Mozilla/5.0 (X11; Linux i686;
 rv:25.0) Gecko/20100101 Firefox/25.0)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Dec 2013 21:30:15 -0000

jb <jb.1234abcd <at> gmail.com> writes:

> ... 
> 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())

Actually, the REALLOCF_ANY flag is not needed to be able to call default
behavior, like in realloc_flags(p, s).

>   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

So, the REALLOCF_FALLBACK_ANY could be just renamed to REALLOCF_DEFAULT.
This way we reduced the number of option tags to four :-)
jb