From owner-freebsd-current Mon Jan 4 20:09:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23894 for freebsd-current-outgoing; Mon, 4 Jan 1999 20:09:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23889 for ; Mon, 4 Jan 1999 20:09:55 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA91110; Mon, 4 Jan 1999 20:09:25 -0800 (PST) (envelope-from dillon) Date: Mon, 4 Jan 1999 20:09:25 -0800 (PST) From: Matthew Dillon Message-Id: <199901050409.UAA91110@apollo.backplane.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: [Commit RFC] More Threads patches. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :There are soem more patches to make FreeBSD's thread support more real. :I would like to add these to those already committed. :Note that this functionality is also useful for FreeBSD native threading :and the native FreeBSD port of the Linuxthreads package. : :The patches are a present conditional on the existance of VM_STACK :and VM_USE_STACK_FOR_EXEC and VM_USE_STACK. This provides a level of :safety to users who are not experimenting with this code by allowing :them to create kernels that are "unchanged". : :The patches I propose to add are at: :http://lt.tar.com/vmsdiff :with :further descriptions availabel at: :http://lt.tar.com/ : :promise to test them better this time :-) I think this would be perfect for the new -current, post-split. There are a bunch of people, including me, who are holding onto pretty major patchsets to commit into the new -current after the split. I'm not crossing my fingers on stability -- I fully expect there to be some problems considering that you, me, Eivind, and I think John intend to do some serious commits into the new -current branch. I expect in about 6-12 months the revamped VM system in the new -current will be moved into the new -stable wholesale. This is my dream, anyway :-) In anycase, you have the opportunity to get your stuff into a true test kernel, allow other people to munch on it for a month or two, and then (considering the relative simplicity of your changes), fold it into the new -stable. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message