[lkml]   [2000]   [Sep]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee
Ted writes:
>Trond Myklebust writes:
> Would it perhaps make sense to use one of these last 'free' fields
> as a pointer to an 'inode entension'?
> If you still want ext2fs to be able to accommodate new projects and
> ideas, then it seems that being able to extend the inode is a
> desirable feature, but perhaps this overlaps with the apparent plans
> for adding resource forks?
> For stuff that's not commonly used, perhaps. The problem is that you
> take a speed hit when you have to seek somewhere else to get at the
> inode extension. So for something which is going to have to be
> referenced for every stat() or getattr() operation, there are a real
> performance issues with doing something like that.

Note that there is already a patch for extended attributes for ext2.
These EAs are used for ACL support, but can be used for a variety of
other extensions to ext2. As Ted indicates, the EAs are stored in another
block, so it will reduce performance if the block is not already in

Cheers, Andreas
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?" -- Dogbert
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.027 / U:2.724 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site