lkml.org 
[lkml]   [2000]   [Sep]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee
   Date: Thu, 14 Sep 2000 15:09:35 +0200 (CEST)
From: Trond Myklebust <trond.myklebust@fys.uio.no>

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.

- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

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