From owner-freebsd-arch@FreeBSD.ORG  Thu Sep  4 14:40:30 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
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 28AE816A4C0; Thu,  4 Sep 2003 14:40:30 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6D41643FCB; Thu,  4 Sep 2003 14:40:28 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h84LeITI002999;
	Thu, 4 Sep 2003 23:40:19 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Andrew Gallatin <gallatin@cs.duke.edu>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 04 Sep 2003 17:34:30 EDT."
             <16215.45030.31344.503298@grasshopper.cs.duke.edu> 
Date: Thu, 04 Sep 2003 23:40:18 +0200
Message-ID: <2998.1062711618@critter.freebsd.dk>
cc: arch@freebsd.org
cc: current@freebsd.org
Subject: Re: DISCUSSION: /dev/fd%d.%d and /dev/{a}cd%d[ac] to be
	discontinued ? 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2003 21:40:30 -0000

In message <16215.45030.31344.503298@grasshopper.cs.duke.edu>, Andrew Gallatin 
writes:

>Can you give a hint as to what you mean by the significant buf/VM
>system changes?  Are you talking about removing the vnode detour for
>drivers and giving drivers who want it access to the struct file?

Well, there really isn't more than that at this point, we plan to talk
about it at BSDcon03 and try to settle on our strategy for the entire
area, and if we manage that we'll communicate it of course.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.