From owner-freebsd-arch Wed Feb 27 8:44: 9 2002 Delivered-To: freebsd-arch@freebsd.org Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by hub.freebsd.org (Postfix) with ESMTP id 774FC37B417 for ; Wed, 27 Feb 2002 08:44:03 -0800 (PST) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.11.4/8.9.3) with ESMTP id g1RGi1i32186; Wed, 27 Feb 2002 08:44:01 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200202271644.g1RGi1i32186@beastie.mckusick.com> To: Jeff Roberson Subject: Re: Slab allocator Cc: arch@FreeBSD.ORG In-Reply-To: Your message of "Wed, 27 Feb 2002 04:00:43 EST." <20020227040002.L17591-100000@mail.chesapeake.net> Date: Wed, 27 Feb 2002 08:44:01 -0800 From: Kirk McKusick 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 Your slab allocator work looks very interesting. Given that the performance is comparable to what we are currently running, it seems like a big step forward. The current statistics that I find most useful are (in order), the number of current allocations, the high watermark for allocations, and the total number of allocations made. The number of current allocations needs to be correct and should be done under a lock. The high watermark and total number of allocations need not be precisely correct, so could well be done without a lock. The occational missed count, or a slightly low high watermark would not much matter. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message