From owner-freebsd-arch Mon Apr 8 1:25: 7 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by hub.freebsd.org (Postfix) with ESMTP id 91BED37B405 for ; Mon, 8 Apr 2002 01:25:04 -0700 (PDT) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g388P4Z80340 for ; Mon, 8 Apr 2002 04:25:04 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Mon, 8 Apr 2002 04:25:03 -0400 (EDT) From: Jeff Roberson To: arch@freebsd.org Subject: Removing limits from malloc(9) Message-ID: <20020408041726.U53877-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The last bit that is missing before we can call malloc/free w/o Giant is the malloc_type statistics. Currently there is nothing really protecting them. There really is no lock that they can conveniently live under. I have a few options. The one that I'm leaning towards is only enabling malloc_type statistics if INVARIANTS is compiled in. Then I could make one lock per malloc_type. The reason this shouldn't be the default is because it creates a single point of contention which is in sharp contrast with the rest of the allocator. So, the INVARIANTS only option doesn't work if we want to keep malloc type limits. I'm wondering how useful this has been in the past? I have heard from phk that it is useful for md(4) which could be converted to use a zone. Is there any real need for these limits other than that? Any comments? Suggestions? Thanks! Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message