From owner-freebsd-current Sat Feb 23 18: 8:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 76AA037B404; Sat, 23 Feb 2002 18:08:15 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id NAA04292; Sun, 24 Feb 2002 13:08:09 +1100 Date: Sun, 24 Feb 2002 13:08:26 +1100 (EST) From: Bruce Evans X-X-Sender: To: Matthew Dillon Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) In-Reply-To: <200202240051.g1O0p3E16932@apollo.backplane.com> Message-ID: <20020224130010.W31250-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Feb 2002, Matthew Dillon wrote: > :It's too messy and unfinished (doesn't work right for SMP or irqs >= 16), > :and dificult to untangle from my other patches. I posted these partial > :ones to attempt to inhibit() recomplication of the current critical* > :functions in directions that I don't want to go :-). > > Oh, ok. Hmm. Well, do you mind if I throw together an interrupt-set-cli- > in-return-frame patch set? I think it would wind up being just as fast. I don't see how that would work. We need to call critical_enter() from ordinary code, so there is no free frame pop. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message