From owner-freebsd-fs Wed Nov 13 06:49:51 1996 Return-Path: owner-fs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA19939 for fs-outgoing; Wed, 13 Nov 1996 06:49:51 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA19926; Wed, 13 Nov 1996 06:49:46 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.2/CET-v2.1) with SMTP id OAA15158; Wed, 13 Nov 1996 14:49:44 GMT Date: Wed, 13 Nov 1996 23:49:43 +0900 (JST) From: Michael Hancock To: FreeBSD Hackers cc: freebsd-fs@FreeBSD.ORG Subject: NFS bypass op and the utok layer Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Were these even considered when the FreeBSD vnode stacking implementation was done? The NFS default op is the one returning the NOT SUPPORTED error. A bypass op would allow you to stack on top of an out-of-kernel layer which could then be layered on a utok layer to cross the boundary again. I guess the fs memory allocation architecture is not compatible with this. Debugging in userland would sure be cool, when you're satisfied take away the transport layers and you're back in the kernel. Regards, Mike Hancock