From owner-freebsd-stable@FreeBSD.ORG Thu Mar 28 05:39:22 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EFE79501 for ; Thu, 28 Mar 2013 05:39:22 +0000 (UTC) (envelope-from unga888@yahoo.com) Received: from nm4-vm0.bullet.mail.bf1.yahoo.com (nm4-vm0.bullet.mail.bf1.yahoo.com [98.139.213.129]) by mx1.freebsd.org (Postfix) with SMTP id 93C6F957 for ; Thu, 28 Mar 2013 05:39:22 +0000 (UTC) Received: from [98.139.215.141] by nm4.bullet.mail.bf1.yahoo.com with NNFMP; 28 Mar 2013 05:39:16 -0000 Received: from [98.139.212.207] by tm12.bullet.mail.bf1.yahoo.com with NNFMP; 28 Mar 2013 05:39:16 -0000 Received: from [127.0.0.1] by omp1016.mail.bf1.yahoo.com with NNFMP; 28 Mar 2013 05:39:16 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 583399.47248.bm@omp1016.mail.bf1.yahoo.com Received: (qmail 50897 invoked by uid 60001); 28 Mar 2013 05:39:16 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1364449156; bh=W1lL8/UaPbZI72IbCdyDxdAMMyy7sDTQMM2FIiAP4BU=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=6k03cRnMA00nxDcRWeELQ8+gwhLTgQWjC35eiALfhRdOmWIezfL8GFZK1bg7OHP3AGwmMguQAIv8XTHMNtlvA6Q0iWXrFwH+mr1n43BJRWXMMdVvsHUCyksqeagZNh6tyE5Im53zNqnpbqOctIxgHCjwDVajwYmxNPj4tysfF0k= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=4+xlLlXuv+X6SsQI8lnnRdi5HMaI9tta9gZd4i+cyON9fvUrIqTsaNZYKsTxfgVis2NMHJxLG09BPGLG3/ZSbMEOo61NhMr9uvPE4aeioYX0SJ+j+JNcCa4CyXcx5dEUXpGhIPBFEcv0pB+zIz4xoQrpB2sFXRwfU6Vs6k2ENTU=; X-YMail-OSG: Fef0m90VM1mDEx5TiNlgpYiWVL6Myr9BcoxyphM6iDpTCTj JVL4Fot3VdP30jwWX91HXK8ZNWp2_cQ66hAYrpDs_8WbVkJ7ehACWEEHU4FD EmeLCH6cqalzPgYOSnJ.gjCbkKBkJjG9cELtATQfhH142Y8XOwySanoz_dq0 gg42qp1jrI8xfcCIJnxI30XIuro2dZnIa2kLXJeCEapP_r2._3eH3siZyJcS z1U2xsrLc7ZOIB3BHDv.gfcEkLk2Fb3CZIGLJIPgGH0MapnSfhBTxjteeZPq .kCQTlTguJMDzpNSfnga7Iv5dt8sFSN_Hovcn42mFQV19ticZIye8vZpK5o_ 834xzPkJlEpW6STfLDjsGcIXaZw.BE4hTewCS9ql1E90tKLLOpTTgKXLqIhQ OCvMmqWfNWFRORC8UkBvv47m75dC3XM0WVyi1dh_bAlGsUkRCtuD5M2eUYp. MTI84b1XQDPiZOQqUMOGdfXPKvqSo3cJ08_ZwvpvYAU.9t7Gy37k21JqZRzv dWJfCbB0Vcy7IPAxO5kI- Received: from [112.134.200.112] by web161906.mail.bf1.yahoo.com via HTTP; Wed, 27 Mar 2013 22:39:16 PDT X-Rocket-MIMEInfo: 002.001, Cgo.IAoKPiBJIHRoaW5rIHlvdSBtYXkgYmUgcmVhZGluZyB0b28gbXVjaCBpbnRvIHRoZSBtYWxsb2MgbWFucGFnZS7CoCBXaGVuIGl0Cj4gbWVudGlvbnMgdGhlIHVzZSBvZiBwZXItdGhyZWFkIHNtYWxsLW9iamVjdCBjYWNoZXMgdG8gYXZvaWQgbG9ja2luZyBpdCdzCj4gdGFsa2luZyBhYm91dCBwZXJmb3JtYW5jZSwgbm90IHRocmVhZCBzYWZldHkuwqAgQWxsb2NhdGlvbnMgb2YgYWxsIHNpemVzCj4gYXJlIHRocmVhZC1zYWZlLCB0aGUgbGlicmFyeSBqdXN0IGFzc3VtZXMgdGhhdCBodWdlIGFsbG9jYXQBMAEBAQE- X-Mailer: YahooMailWebService/0.8.139.530 References: <1364322902.78474.YahooMailNeo@web161904.mail.bf1.yahoo.com> <1364393170.36972.49.camel@revolution.hippie.lan> <1364409226.37379.YahooMailNeo@web161906.mail.bf1.yahoo.com> <1364410923.36972.67.camel@revolution.hippie.lan> Message-ID: <1364449156.30979.YahooMailNeo@web161906.mail.bf1.yahoo.com> Date: Wed, 27 Mar 2013 22:39:16 -0700 (PDT) From: Unga Subject: Re: FreeBSD 9.1 excessive memory allocations [SOLVED] To: "freebsd-stable@FreeBSD.org" In-Reply-To: <1364410923.36972.67.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Unga List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Mar 2013 05:39:23 -0000 =0A=0A> =0A=0A> I think you may be reading too much into the malloc manpage= .=A0 When it=0A> mentions the use of per-thread small-object caches to avoi= d locking it's=0A> talking about performance, not thread safety.=A0 Allocat= ions of all sizes=0A> are thread-safe, the library just assumes that huge a= llocations are rare=0A> enough that it doesn't use extra per-thread resourc= es to avoid locking=0A> for them, it just uses locking for huge blocks.=0A>= =0A> -- Ian=0A>=0A=0AGood to note all allocations are thread safe in FreeB= SD. Is it by some standard that malloc should be thread safe regardless the= OS (BSDs, Linux, Windows, Android, etc)?=0A=0AUnga=0A