From owner-freebsd-arch Thu Jul 13 23:35:57 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id C7DE437BDEC for ; Thu, 13 Jul 2000 23:35:53 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA00783; Thu, 13 Jul 2000 23:44:04 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007140644.XAA00783@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John-Mark Gurney Cc: Boris Popov , Andrzej Bialecki , freebsd-arch@freebsd.org Subject: Re: SysctlFS In-reply-to: Your message of "Thu, 13 Jul 2000 12:12:08 PDT." <20000713121208.50527@hydrogen.funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Jul 2000 23:44:03 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > /bus - newbus tree > > I think it's wrong to assume that this is a tree... I would like to > see it move to a graph based structure... as we start off loading > parts of processing, we will no longer have such an obvious nexus.. I don't think it has anything to do with "offloading parts of processing", but if we ever end up running on a switched fabric architecture, parts of the bus hierarchy aren't going to look very tree-like. > Each cpu should be the "root" of it's own tree... but that's just my > view on the world.. :) And one that's hopelessly incompatible with the way things work, unfortunately -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message