Skip site navigation (1)Skip section navigation (2)
Date:      08 Apr 2002 10:41:04 +0200
From:      Dag-Erling Smorgrav <des@ofug.org>
To:        Jeff Roberson <jroberson@chesapeake.net>
Cc:        arch@freebsd.org
Subject:   Re: Removing limits from malloc(9)
Message-ID:  <xzplmbyr3a7.fsf@flood.ping.uio.no>
In-Reply-To: <20020408041726.U53877-100000@mail.chesapeake.net>
References:  <20020408041726.U53877-100000@mail.chesapeake.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Jeff Roberson <jroberson@chesapeake.net> writes:
> 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.

It's still a lot better than Giant, and it's a leaf lock so there
shouldn't be any worries about reversal.  I'd go for it if I were you.

DES
-- 
Dag-Erling Smorgrav - des@ofug.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzplmbyr3a7.fsf>