On Wed, May 02, 2001 at 04:49:30PM +0200, Andi Kleen wrote:
On Mon, Apr 30, 2001 at 12:39:23PM -0600, Matthew Wilcox wrote:
* All filesystems will fill in their -lock method.
Why when a common stub should work for 90% of them? Please keep
global search-and-edit operation low when not
I'm not going to change it from a linear list until I've made these other
changes. In the meantime, if anyone knows of a data structure which lets
me
record ranges and check for overlaps, let me know...
Would a threaded AVL tree (http://www.msu.edu/user/pfaffben/avl/) be over
the top? I'd
On Wed, 2 May 2001, Matthew Wilcox wrote:
I never understood why you can't do it completely inode local protected
by the inode lock; but then I don't claim that I understand fs/locks.c
inode_lock claims it's for protecting the list manipulations, not for
protecting any element in an
I don't think that an AVL tree will work, at least without substantial
modification, for three reasons: (1) the intervals stored don't have to be
disjoint (read locks can overlap), (2) the overlap detection is
problematic (note that you're looking for overlaps only with a different
lockowner
On Thursday 03 May 2001 03:15, you wrote:
Hello Daniel,
This combination against 2.4.4 won't allow directories to be moved.
Ex: mv a b #fails with I/O error. See attached strace.
But with ext2-dir-patch-S4 by itself, mv works as it should.
Later,
Albert
Thanks Albert, this was easily
