From owner-freebsd-arch@FreeBSD.ORG Fri Mar 4 00:34:26 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 C561E16A4CE; Fri, 4 Mar 2005 00:34:26 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2133243D1F; Fri, 4 Mar 2005 00:34:22 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j240aHFA007283; Thu, 3 Mar 2005 17:36:17 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4227AC82.7000606@samsco.org> Date: Thu, 03 Mar 2005 17:32:02 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <20050303074242.GA14699@VARK.MIT.EDU> <200503030954.08271.jhb@FreeBSD.org> <20050303165825.GB4737@odin.ac.hmc.edu> <42279DEF.2030901@freebsd.org> In-Reply-To: <42279DEF.2030901@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org 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: Fri, 04 Mar 2005 00:34:26 -0000 David Xu wrote: > 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. :) The kernel is not a POSIX C environment. It's not just a program that happens to do special things. I know that Linux goes to great lengths to support this concept, but it's simply not true. Programming in the kernel ideally is not much different from other forms of embedded system programming where resources are finite and expensive and it's the responibility of the programmer to develop efficient and safe code. Scott