From owner-freebsd-arch@FreeBSD.ORG Thu Mar 27 14:49:56 2003 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 8A00237B401 for ; Thu, 27 Mar 2003 14:49:56 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FD5843F75 for ; Thu, 27 Mar 2003 14:49:55 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.8/8.12.8) with ESMTP id h2RMnsRv011567 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 27 Mar 2003 17:49:54 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h2RMnnY18612; Thu, 27 Mar 2003 17:49:49 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16003.32780.950519.931661@grasshopper.cs.duke.edu> Date: Thu, 27 Mar 2003 17:49:48 -0500 (EST) To: Daniel Eischen In-Reply-To: References: <20030327143259.I64602-100000@mail.chesapeake.net> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid X-Spam-Status: No, hits=-22.9 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: arch@freebsd.org Subject: Re: 1:1 threading. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: arch@freebsd.org List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Mar 2003 22:49:57 -0000 Daniel Eischen writes: > On Thu, 27 Mar 2003, Jeff Roberson wrote: > > > On Thu, 27 Mar 2003, Daniel Eischen wrote: > > > > Which means they are likely to change. I do not want to develop on > > unstable APIs and unstable kernel code. kern_thr.c is 254 lines. I think > > we can handle a little duplication. I'm not sure why the objection is so > > strong. > > I don't see kse_create() changing since it takes a > mailbox pointer as an argument and you can theoretically > hang anything off the [versioned] mailbox. According to the 5-stable roadmap at http://www.freebsd.org/doc/en/articles/5-roadmap/major-issues.html KSE kernel and userland components must be functionality complete by June 2003 in order to be included in the RELENG_5 branch. For security and stability reasons, if KSE cannot be finished in time then, by default, all KSE-specific syscalls should be modified to return ENOSYS and all other KSE-specific interfaces disabled. By not depending on KSE infastructure, the 1:1 can still be available in 5.1 in exactly the same fore regardless of whether or not KSE makes the June deadline or not. Drew