From owner-cvs-all@FreeBSD.ORG Sat Mar 5 10:12:11 2005 Return-Path: Delivered-To: cvs-all@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id D261416A4CF; Sat, 5 Mar 2005 10:12:11 +0000 (GMT) Date: Sat, 5 Mar 2005 10:12:11 +0000 From: Alexey Dokuchaev To: David Xu Message-ID: <20050305101211.GA59471@FreeBSD.org> References: <200503050915.j259F30c058488@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200503050915.j259F30c058488@repoman.freebsd.org> User-Agent: Mutt/1.4.2.1i cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sys proc.h umtx.h src/sys/kern kern_thread.c kern_umtx.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2005 10:12:12 -0000 On Sat, Mar 05, 2005 at 09:15:03AM +0000, David Xu wrote: > davidxu 2005-03-05 09:15:03 UTC > > FreeBSD src repository > > Modified files: > sys/sys proc.h umtx.h > sys/kern kern_thread.c kern_umtx.c > Log: > Allocate umtx_q from heap instead of stack, this avoids > page fault panic in kernel under heavy swapping. So.. Slow malloc/free path at last. As a side note, could someone (not necessarily David) comment on my impression that, for example, recently reported not-so-optimal performance of our threading model(s) is largely due to heavy use of malloc/free, as opposed to other operating systems out there? Am I right thinking that this is main bottleneck? If malloc'ing is so costly, why we're taking this path? Can kernel malloc() be optimized? Thanks. ./danfe