[OpenAFS-devel] RE: [OpenAFS] Strange Behavior of Openafs-1.1 .1

[Neulinger, Nathan]

So basically, we're reproducing an entire structure, plus constantly
maintaining it, just so that we can save some memory? ick.

Seems to me that we'd be better off putting more intelligence into the part
of the code that allocate's the new vnode's and just have it not allocate as
big a piece. (i.e. use something like XtOffsetOf() in a malloc).

-- Nathan

> -----Original Message-----
> From: Jeffrey Hutzelman [mailto:jhutz@cmu.edu]
> Sent: Wednesday, August 08, 2001 2:18 PM
> To: Neulinger, Nathan
> Cc: 'openafs-devel@openafs.org'
> Subject: RE: [OpenAFS-devel] RE: [OpenAFS] Strange Behavior of
> Openafs-1.1 .1
> 
> 
> On Wed, 8 Aug 2001, Neulinger, Nathan wrote:
> 
> > I just took another look over fs.h and osi_vfs.h and I'm confused...
> > 
> > What fields are the extra data that AFS is adding? Looks to 
> me like struct
> > vnode_t is 100% identical to the existing struct inode, 
> with the exception
> > that the fs-specific union appears to be alot smaller in 
> the vnode_t one. 
> 
> That's essentially correct.  The problem is that the union is 
> quite large,
> so there's a lot of overhead to including that extra space in 
> every vnode.
> 
> -- Jeff
>