From owner-freebsd-current@FreeBSD.ORG  Sun Dec  1 03:05:02 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 8C09EFD9
 for <freebsd-current@freebsd.org>; Sun,  1 Dec 2013 03:05:02 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 225C81AFC
 for <freebsd-current@freebsd.org>; Sun,  1 Dec 2013 03:05:02 +0000 (UTC)
Received: from [157.181.98.186] ([157.181.98.186]) by mail.gmx.com (mrgmx101)
 with ESMTPSA (Nemesis) id 0MAUpK-1Vsygw0lEA-00Bblb for
 <freebsd-current@freebsd.org>; Sun, 01 Dec 2013 04:05:00 +0100
Message-ID: <529AA73A.9@gmx.com>
Date: Sun, 01 Dec 2013 04:04:26 +0100
From: dt71@gmx.com
User-Agent: Mozilla/5.0 (X11; FreeBSD i386;
 rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20
MIME-Version: 1.0
To: Luigi Rizzo <rizzo@iet.unipi.it>, Adrian Chadd <adrian@freebsd.org>, 
 freebsd-current <freebsd-current@freebsd.org>, jb <jb.1234abcd@gmail.com>
Subject: Re: [RFC] how to get the size of a malloc(9) block ?
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>
 <CAJ-Vmon2dy94jCUwrBjObrxahmaTyqYZJZo4Lren2Km_vX3_OA@mail.gmail.com>
 <CA+hQ2+i7woEM9x7Ymo+D4FbG2rn0eRYnX=7mUTrPjDqj-pme7A@mail.gmail.com>
 <20131201022002.GE55638@funkthat.com>
In-Reply-To: <20131201022002.GE55638@funkthat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:ZTco5Bl8PIVK9r7U9E0d92mmHH3WeNq4Zvshq3/nCtaKKm2iLRE
 sxK7VxdTVNHa/ajB8USuJ+dzpJoVR3R160PQZ9ihKEl1c/vk6W+ul274FYdQ2GLMhu3q+sI
 jFJmVYmIGMdxCxpkUi6BLYcPEsGD9egeubEtv3aTcx+txMqzilkrfi07XjO/wMXvhljER1A
 IePwd3/28UhHXWs5UbpQA==
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.16
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: Sun, 01 Dec 2013 03:05:02 -0000

John-Mark Gurney wrote, On 12/01/2013 03:20:
> Either it happens rarely, and always doing a realloc won't hurt
> performance, or it happens often, and then you should be using a larger
> buffer in the first place..

What if a size-elastic implementation of a dynamic data structure would be able to adjust to the malloc implementation, such as agreeing to allocate regions of size (2^k - 8)? Much like the use of getpagesize() (yes, I know it's not part of a technical standard).