From owner-freebsd-current@FreeBSD.ORG  Sun Dec  1 02:20:06 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 0012E65B;
 Sun,  1 Dec 2013 02:20:05 +0000 (UTC)
Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id B04BB18B8;
 Sun,  1 Dec 2013 02:20:05 +0000 (UTC)
Received: from h2.funkthat.com (localhost [127.0.0.1])
 by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id rB12K3H6073939
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Sat, 30 Nov 2013 18:20:04 -0800 (PST)
 (envelope-from jmg@h2.funkthat.com)
Received: (from jmg@localhost)
 by h2.funkthat.com (8.14.3/8.14.3/Submit) id rB12K39R073938;
 Sat, 30 Nov 2013 18:20:03 -0800 (PST) (envelope-from jmg)
Date: Sat, 30 Nov 2013 18:20:03 -0800
From: John-Mark Gurney <jmg@funkthat.com>
To: Luigi Rizzo <rizzo@iet.unipi.it>
Subject: Re: [RFC] how to get the size of a malloc(9) block ?
Message-ID: <20131201022002.GE55638@funkthat.com>
Mail-Followup-To: Luigi Rizzo <rizzo@iet.unipi.it>,
 Adrian Chadd <adrian@freebsd.org>,
 freebsd-current <freebsd-current@freebsd.org>,
 jb <jb.1234abcd@gmail.com>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+hQ2+i7woEM9x7Ymo+D4FbG2rn0eRYnX=7mUTrPjDqj-pme7A@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Operating-System: FreeBSD 7.2-RELEASE i386
X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88  9322 9CB1 8F74 6D3F A396
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger?
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
 (h2.funkthat.com [127.0.0.1]); Sat, 30 Nov 2013 18:20:04 -0800 (PST)
Cc: Adrian Chadd <adrian@freebsd.org>,
 freebsd-current <freebsd-current@freebsd.org>, jb <jb.1234abcd@gmail.com>
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 02:20:06 -0000

Luigi Rizzo wrote this message on Fri, Nov 29, 2013 at 17:11 -0800:
> On Fri, Nov 29, 2013 at 4:49 PM, Adrian Chadd <adrian@freebsd.org> wrote:
> 
> > The reason I wouldn't implement this is to avoid having code that
> > _relies_ on this behaviour in order to function or perform well.
> 
> 
> nobody ever said (or could reasonably expect to do) that.
> 
> Applications don't know if the allocator overallocates,
> so they have no hope unless they work even without the feature.
> 
> This is only about giving them an option to improve
> performance in those (rare ?) cases where, as i showed,
> knowing the underlying allocation size may lead to
> better usage of memory.

This sounds like optimizing before measuring if your putting in code
like that...

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

Do I need to quote the optimization rules?

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."