From owner-freebsd-current Wed Sep 12 8:20:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C608137B401 for ; Wed, 12 Sep 2001 08:20:29 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id IAA58738; Wed, 12 Sep 2001 08:54:33 -0700 (PDT) Date: Wed, 12 Sep 2001 08:54:32 -0700 (PDT) From: Julian Elischer To: Mark Santcroos Cc: current@FreeBSD.ORG Subject: Re: HEADSUP!!!! KSE Milestone-2 COMMITTED In-Reply-To: <20010912131506.A582@laptop.6bone.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG yes I believe so... On Wed, 12 Sep 2001, Mark Santcroos wrote: > Hi Julian, > > I didnt try the latest "thediff's", but did you solve the panic at reboot > issue? > > Mark > > > On Wed, Sep 12, 2001 at 02:17:13AM -0700, Julian Elischer wrote: > > > > If you've been ignoring KSE till now you can do so for a little longer, > > but you should look at: > > A very slightly out-of-date paper describing what KSE will become: > > http://www.freebsd.org/~jasone/kse/ > > http://www.freebsd.org/~julian/ has some links of interest too. > > > > All modules must be recompiled. > > > > I'm waiting for it to all trickle back to me via the cvsup chain > > at which point I'll be doing more "make world"s and further tests. > > (it was tested before commit but you never know what can happen > > between the last test and the checkout..) > > It's been a hard day getting all the checks done. > > I'll try stay awake for a while longer in case things break but > > if I can't keep my eyes open much longer, I'll be back online in 7 hours or so.. > > > > KSE Milestone 2 definition: > > Milestone 2 is the last point in development where all algorythms used in the > > kernel are identical to that used in the non-kse kernel. > > i.e. While it looks very different, the fact that there is by defintition > > 1 thread per process at all times ensures that this kernel acts the same as > > its predecessor. Before we can become multithreaded we have to start > > changing the algorythms involved in many parts of the kernel. > > By checking in at this point we ensure a minimal diff set to the > > development work but still ensure a reliable checkpoint. > > > > > > > > -- > > +------------------------------------+ ______ _ __ > > | __--_|\ Julian Elischer | \ U \/ / hard at work in > > | / \ julian@elischer.org +------>x USA \ a very strange > > | ( OZ ) \___ ___ | country ! > > +- X_.---._/ presently in San Francisco \_/ \\ > > v > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Mark Santcroos RIPE Network Coordination Centre > http://www.ripe.net/home/mark/ New Projects Group/TTM > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message