From owner-freebsd-current  Sat Feb 23 17:59:49 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 13BBE37B402; Sat, 23 Feb 2002 17:59:46 -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 MAA03882;
	Sun, 24 Feb 2002 12:59:39 +1100
Date: Sun, 24 Feb 2002 12:59:55 +1100 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender:  <bde@gamplex.bde.org>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Terry Lambert <tlambert2@mindspring.com>,
	Alfred Perlstein <alfred@FreeBSD.ORG>,
	Bosko Milekic <bmilekic@unixdaemons.com>,
	Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp>,
	<current@FreeBSD.ORG>, John Baldwin <jhb@FreeBSD.ORG>
Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.)
In-Reply-To: <200202240049.g1O0noD15327@apollo.backplane.com>
Message-ID: <20020224125005.N31250-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: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On Sat, 23 Feb 2002, Matthew Dillon wrote:

>     Bruce, I've looked at the vector assembly and it looks like cleaning
>     up critical_enter() and critical_exit() for i386 ought to be simple.
>
>     If you have a complete patch set I would like to see it posted for
>     review or comitted, or if you don't want to deal with the commit I
>     would love to have it so I can bang it into shape for commit.

Patches for most of my sys tree are in sys.tar.gz in my home directory
on freefall.

>     Having a sleek critical_enter()/critical_exit() would double sched_lock's
>     performance.

I'm not sure about that.  Perhaps I've already optimized sched_lock
enough that I don't notice.  My changes were actually directed at
avoiding sched_lock's interrupt latency and it wasn't until the
critical_enter()/ exit() calls pessimized mtx_{lock,unlock}_spin in
-current that I managed to share enough code (the critnest
increment/decrement) to avoid losing efficiency.

Bruce


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