From owner-freebsd-arch Fri Mar 1 12:36:53 2002 Delivered-To: freebsd-arch@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C8BEF37B402 for ; Fri, 1 Mar 2002 12:36:49 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g21KaIs46295; Fri, 1 Mar 2002 12:36:18 -0800 (PST) (envelope-from dillon) Date: Fri, 1 Mar 2002 12:36:18 -0800 (PST) From: Matthew Dillon Message-Id: <200203012036.g21KaIs46295@apollo.backplane.com> To: Julian Elischer Cc: Jeff Roberson , arch@FreeBSD.ORG Subject: Re: Slab allocator update References: 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 :On Wed, 27 Feb 2002, Jeff Roberson wrote: : :> :> 1) Fix the last lock order reversal. :> 2) Fixup the statistics for uma and malloc. :> 3) Convince people to test it. :> 4) Commit. : :Please try integrate it in such a form that both new and old can be :compiled in with a config option. :(for a while) : :> 5) Work on converting everything to uma_* interfaces, and adding :> initializers. : :Do lots of testingto prove that it's an improvement. I think it only needs to have 'similar' performance to be an improvement, since the eventual goal is to collapse the kernel malloc and zalloc subsytems into one. Right now we have rather serious issues with KVM exhaustion. The fact that the existing kernel malloc uses kmem_map and zalloc uses kernel_map for expansion, and that none of the memory is ever returned, is one of the primary culprits. I would happy if that mess were consolidated into one universal allocation mechanism capable of returning memory to the system even if it meant a slight loss in performance. I'm not sure I agree with an integration that tries to keep the old mechanisms alive. If it's easy to do, then sure. But otherwise we should just grin and bear it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message