From owner-freebsd-arch@FreeBSD.ORG Thu Mar 3 23:29:53 2005 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B75D16A4CE; Thu, 3 Mar 2005 23:29:53 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1371C43D31; Thu, 3 Mar 2005 23:29:53 +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 j23NTm89078083; Thu, 3 Mar 2005 23:29:50 GMT (envelope-from davidxu@freebsd.org) Message-ID: <42279DEF.2030901@freebsd.org> Date: Fri, 04 Mar 2005 07:29:51 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.2) Gecko/20041004 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <20050303074242.GA14699@VARK.MIT.EDU> <200503030954.08271.jhb@FreeBSD.org> <20050303165825.GB4737@odin.ac.hmc.edu> In-Reply-To: <20050303165825.GB4737@odin.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: David Schultz cc: freebsd-arch@freebsd.org Subject: Re: Removing kernel thread stack swapping X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 23:29:53 -0000 Brooks Davis wrote: >On Thu, Mar 03, 2005 at 09:54:07AM -0500, John Baldwin wrote: > > >>Hence, don't kill this whole feature just because someone is too lazy >>to fix a bug. >> >> > >It would be very useful and informative if someone were to write a >high level description of the ways in which the kernel is not a POSIX C >programming environment. > when you are importing a POSIX C programmed piece of code into kernel, this will be a problem, I always think problem from another side, not just stand at my side. :) > In addition to providing somewhere to point >people who wonder why -lbigcomplicatedlibrary doesn't work with their >kernel source, such a list would force us to enumerate those differences >and make sure they are based on design decisions that make sense. > >-- Brooks > > >