From owner-freebsd-current@FreeBSD.ORG Fri Mar 4 01:21:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D45F16A4CE; Fri, 4 Mar 2005 01:21:17 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D9DF43D2F; Fri, 4 Mar 2005 01:21:17 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j241LCGh099114; Fri, 4 Mar 2005 01:21:15 GMT (envelope-from davidxu@freebsd.org) Message-ID: <4227B7F8.9090304@freebsd.org> Date: Fri, 04 Mar 2005 09:20:56 +0800 From: David Xu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Dillon References: <200503040103.j2413CNr082179@apollo.backplane.com> In-Reply-To: <200503040103.j2413CNr082179@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: alc@freebsd.org cc: freebsd-current@freebsd.org cc: Robert Watson cc: peter@freebsd.org Subject: Re: FreeBSD 5.3 crash (core with debug symbols available) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 01:21:17 -0000 Matthew Dillon wrote: > The main reason we no longer swap the kernel stack is because there are > a whole lot of things we put on local thread stacks that other parts of the > system may reference even while the process is blocked. e.g. token > references, message structures, register or FP save state, and so forth. > I also intend to put cache related structures, such as range locks, on > the stack. I just didn't want to have to worry about it. > > Besides, it only happened when a process was actually *SWAPPED* out, not > just heavily paged, and how often does *that* happen these days? Even > on a heavily loaded system only a handful of processes, mostly getty's > and long-idle interactive shells, might actually be swapped out. This > makes the memory savings minimal at best. > > > I always worry about swapping out kernel stack. my lastest kernel umtx code is broken by this. I can not agree that per-mutex operation needs a pair of heavy malloc and free call, if kernel mutex performance is important, why userland mutex shouldn't be ? If I have to use malloc, I am afraid that I have to do more extra work than Linux does, I will fail under real world benchmark like super-smack etcs. > -Matt > > > >