Date: Thu, 2 Sep 2004 13:48:31 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Julian Elischer <julian@elischer.org> Cc: Julian Elischer <julian@FreeBSD.org> Subject: Re: cvs commit: src/sys/i386/include param.h Message-ID: <20040902204831.GJ29902@funkthat.com> In-Reply-To: <41376280.6050801@elischer.org> References: <200409011829.i81ITvq9017808@repoman.freebsd.org> <xzp656xlprb.fsf@dwp.des.no> <4136333C.8090207@elischer.org> <20040902175930.GA8551@dragon.nuxi.com> <41376280.6050801@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote this message on Thu, Sep 02, 2004 at 11:12 -0700:
> David O'Brien wrote:
> >What it really means is we haven't provided a sufficient API for userland
> >to get a kernel data that obviously is needed.
>
> yes.. it's tricky..
> should we define a "_KERNEL_INTERFACE" or something?
> how about _REALLY_IS_KERNEL
> which defines _KERNEL
> so if you just need the interface you define _KERNEL
> but include files cna protect REALLY internal stuff with "#ifdef
> _REALLY_IS_KERNEL
The question first is, do we want to use the same structure in userland
and kernel.. If we do, then it should not be under _KERNEL, and be
publicly exported... If we don't need the entire structure, then we
define the common structure, and write a function or two that converts
between the two structures... like struct xfile, struct xprision,
struct xvfsconf, struct xsocket, struct xucred, struct xunpcb,
struct xunpgen, struct xvnode...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040902204831.GJ29902>