From owner-freebsd-fs@FreeBSD.ORG Tue Dec 23 20:16:27 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5F8A1065670 for ; Tue, 23 Dec 2008 20:16:27 +0000 (UTC) (envelope-from gerryw@compvia.com) Received: from mail01.compvia.com (mail01.compvia.com [12.147.132.91]) by mx1.freebsd.org (Postfix) with ESMTP id 8EFF08FC19 for ; Tue, 23 Dec 2008 20:16:27 +0000 (UTC) (envelope-from gerryw@compvia.com) Received: from [10.10.20.11] ([10.10.20.11]) by mail01.compvia.com (Kerio MailServer 6.5.1); Tue, 23 Dec 2008 14:16:26 -0600 To: "Robert Watson" From: "Gerry Weaver" In-Reply-To: alpine.BSF.1.10.0812231138272.90302@fledge.watson.org Message-ID: <20081223201626.caa483ad@mail01.compvia.com> Date: Tue, 23 Dec 2008 14:16:26 -0600 X-Mailer: Kerio MailServer 6.5.1 WebMail X-User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.1b1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Headers files included by vnode.h X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2008 20:16:28 -0000 =5F=5F=5F=5F=5F =20 From: Robert Watson [mailto:rwatson@FreeBSD.org] To: Gerry Weaver [mailto:gerryw@compvia.com] Cc: gary.jennejohn@freenet.de, freebsd-fs@freebsd.org Sent: Tue, 23 Dec 2008 05:41:13 -0600 Subject: Re: Headers files included by vnode.h On Mon, 22 Dec 2008, Gerry Weaver wrote: =20 > Because these files are dynamically generated it makes no sense to > install them. There are quite a few files like these which are use= d > during the kernel generation process to dynamically create include > files. This allows greater flexibility. > > Thanks Gary. I appreciate your help. =20 The usual question here is "what are you trying to do=3F". Normally w= e=20 dynamically generate the implementations of the VOP interfaces when th= e kernel=20 (or a module built independently from the kernel) depends on them. If= you're=20 creating a kernel module, you can add a dependency on vnode=5Fif.h, wh= ich will=20 cause the kernel module build framework to generate local copies of th= e file=20 in your build directory during the build, as seen in the Coda module: =20 # $FreeBSD: src/sys/modules/coda/Makefile,v 1.17.2.1 2008/03/14 17:= 12:40 rwatson Exp $ =20 .PATH: ${.CURDIR}/../../fs/coda =20 KMOD=3D coda SRCS=3D vnode=5Fif.h \ coda=5Ffbsd.c coda=5Fpsdev.c coda=5Fsubr.c coda=5Fvenus.c c= oda=5Fvfsops.c \ coda=5Fvnops.c opt=5Fcoda.h =20 .include =20 If it's for the purposes of debugging a kernel, you should be able to = find the=20 generated copies of the files in the build directory for the kernel. =20 Robert N M Watson Computer Laboratory University of CambridgeHi Robert, Perfect. Yes, I am building a kernel module. This is exactly what I was = looking for.=20 I really appreciate your help.=20 I am also trying to figure out a zero copy approach to kernel memory acc= ess from user space. Would you happen to know which list I should post t= he question to=3F Have a great holiday all. Thanks, Gerry =20