From owner-freebsd-arch@FreeBSD.ORG  Wed Jun 18 09:46:36 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 0485237B401
	for <arch@freebsd.org>; Wed, 18 Jun 2003 09:46:36 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 061AD43F75
	for <arch@freebsd.org>; Wed, 18 Jun 2003 09:46:35 -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 h5IGkRBE041955;
	Wed, 18 Jun 2003 18:46:29 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Julian Elischer <julian@elischer.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Wed, 18 Jun 2003 09:40:25 PDT."
             <Pine.BSF.4.21.0306180938260.5566-100000@InterJet.elischer.org> 
Date: Wed, 18 Jun 2003 18:46:27 +0200
Message-ID: <41954.1055954787@critter.freebsd.dk>
cc: arch@freebsd.org
Subject: 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
	<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: Wed, 18 Jun 2003 16:46:36 -0000

In message <Pine.BSF.4.21.0306180938260.5566-100000@InterJet.elischer.org>, Julia
n Elischer writes:
>cool..
>how does 'mount' do this however, as it doesn't have a fd list to wok
>with. Or are you still leaving the vnode access path in place?

The vnode access path remains in order to support buf/vm

-- 
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.