By "file operations", i did mean vnode operations. "Kernel code" it is. And, yes, i was referring to "VNOP_*"
My usage stands corrected.
----- Original Message ----
From: Michael Smith <email@hidden>
To: Ratheesh Ramachandran <email@hidden>
Cc: Terry Lambert <email@hidden>; email@hidden
Sent: Thursday, June 7, 2007 9:32:59 PM
Subject: Re: Newbie question - missing vop* structures/functions in sys/vnode.h on 10.4
On Jun 7, 2007, at 3:51 AM, Ratheesh Ramachandran wrote:
> Thanks Terry and Michael.
>
> Combining both your
responses:
>
> - Kernel programs should not perform file operations using vop_*
> functions/structures (which is not possible on 10.4 anyway).
>
> - Kernel programs should perform file operations using the vnode_*
> functions (KPI) defined in sys/vnode.h
Kernel code (there are no 'kernel programs' in the jargon) should as
a general rule not perform "file operations" at all.
Typically you will be operating on a vnode, which has previously been
looked up by another function.
> - vnop_* functions are to be implemented by Filesystems, and the
> vnode_* functions (KPI) in turn call these.
The VNOP_* functions are immediate wrappers around the functions
implemented by filesystems, and exported by those filesystems in
their VNOP export tables.
There are, to the best of my recollection, no vnop_* functions
of note.
= Mike