From owner-freebsd-arch@FreeBSD.ORG Wed Jun 18 12:00:35 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 85D8E37B401 for ; Wed, 18 Jun 2003 12:00:35 -0700 (PDT) Received: from regina.plastikos.com (216-107-106-250.wan.networktel.net [216.107.106.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8564243F75 for ; Wed, 18 Jun 2003 12:00:34 -0700 (PDT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-33-235-56.jan.bellsouth.net [67.33.235.56]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by regina.plastikos.com (Postfix) with ESMTP id A72BD6EEB9; Wed, 18 Jun 2003 15:00:33 -0400 (EDT) Received: by mortis.over-yonder.net (Postfix, from userid 100) id 362ED20F03; Wed, 18 Jun 2003 14:00:32 -0500 (CDT) Date: Wed, 18 Jun 2003 14:00:32 -0500 From: "Matthew D. Fuller" To: Poul-Henning Kamp Message-ID: <20030618190032.GG10127@over-yonder.net> References: <20030618174733.GC10127@over-yonder.net> <42575.1055961734@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <42575.1055961734@critter.freebsd.dk> User-Agent: Mutt/1.4.1i-fullermd.1 X-Editor: vi X-OS: FreeBSD cc: arch@freebsd.org Subject: Meta: explain what where when? (was Re: userland access to devices is moving!) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2003 19:00:36 -0000 On Wed, Jun 18, 2003 at 08:42:14PM +0200 I heard the voice of Poul-Henning Kamp, and lo! it spake thus: > In message <20030618174733.GC10127@over-yonder.net>, "Matthew D. Fuller" writes: > > > >Speaking as somebody whose reach of mailing lists notably exceeds his > >grasp (as it always should be; otherwise what fun is it?), I often find > >myself a little in the dark on what these sort of things really /mean/ to > >the system in the end, and I think it would be a nice extension of these > >sort of posts/proposals to have a sentence of summary, along the lines > >of: > > Well, what can I say but: "You're right". > > I do on the other hand not think that emails to arch@ is the best forum > for the in-depth explanations. Oh, absolutely! And to understand an in-depth explanation, I'd have to dig into the code anyway to understand it. I was aiming more at a throwaway statement like, "This will clean up a lot of code and make it easier to understand and debug," or "This straightens out the code structure and let us add more things onto it more easily," or "This will improve performance for things that do a lot of grubbing to /dev nodes. Your dump(8) will run 3% faster." That last is actually more specific than I have in mind. No guarantee, just a general statement of direction. From my armchair, it's fairly easy to give a "75% cleanup, 20% architecture, 5% performance" 3-axis guesstimate of how this moves us forward, and even such a general direction is an enormous aid to those of us who don't really understand where this plugs into the system. Reading the discussion of this change, I'd say "This is a structural cleanup that eliminates some complexity and makes it easier to understand and add onto, with the 'cleanup' features related to the reduced complexity. It may also yield a small real-world performance improvement for things that do a lot of /dev/* fiddling." Just a thumbnail sketch of whether this is moving us down the path, or hacking out thorns that are keeping us from moving down the path, etc. > The "blueprint" articles which I am trying to restart in DĉmonNews > may not be either, but I think they are more the right kind of > forum for it. I am still warming up to the article format, and the > amount of feedback so far has not really given me any feel for how > complex issues I can tackle without the readers just skipping the > article. That's an interesting way to go, and certainly something worthwhile. Poking at the site now, I see the one from May on userland/kernel interfaces; has there been more? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet"