From owner-freebsd-arch  Fri Jun 16 16:43:10 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id E01D237B9D4
	for <freebsd-arch@FreeBSD.ORG>; Fri, 16 Jun 2000 16:43:06 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
	by feral.com (8.9.3/8.9.3) with ESMTP id QAA06863;
	Fri, 16 Jun 2000 16:41:41 -0700
Date: Fri, 16 Jun 2000 16:41:34 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Jason Evans <jasone@canonware.com>
Cc: Chia-liang Kao <clkao@CirX.ORG>, freebsd-arch@FreeBSD.ORG
Subject: Re: kernel thread support
In-Reply-To: <20000616144259.Q47268@blitz.canonware.com>
Message-ID: <Pine.BSF.4.05.10006161640030.2928-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On 16 Jun 2000, Jason Evans wrote:

> On Fri, Jun 16, 2000 at 03:19:56AM +0800, Chia-liang Kao wrote:
> > o Is the model for the scenario described in
> > 
> >   http://www.freebsd.org/~julian/threads/
> > 
> >   the final design decision? (then I think it shall be well documented.)
> 
> We have made some refinements to the model, but in general, it is the same
> idea.  Daniel Eischen and I are working on a paper that gives a reasonable
> overview of the current design.  Hopefully we can get it to a postable form
> in the near future.  However, we're probably going to concern ourselves
> primarily with actually doing the work, rather than telling everybody
> beforehand exactly how we're doing it.

Can please spend some effort into saying what the intents and architecture is
in the paper?

The current newbus stuff and CAM stuff horribly suffer from the fact that
there aren't such documents. I'm currently tearing my hair out trying to
intuit what should have been written down.






To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message