From owner-freebsd-current Sat Feb 23 16:51: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9F52237B405; Sat, 23 Feb 2002 16:51:04 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1O0p3E16932; Sat, 23 Feb 2002 16:51:03 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 16:51:03 -0800 (PST) From: Matthew Dillon Message-Id: <200202240051.g1O0p3E16932@apollo.backplane.com> To: Bruce Evans Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) References: <20020224111043.W30980-100000@gamplex.bde.org> 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: : :> :My version of it does less than this. I only use it to help implement :> :spinlocks. :> :> You put together infrastructure to deal with pending pci interrupts? :> If so, then why not commit it (or at least commit a version #ifdef'd :> for the i386 architecture). : :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. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message