[lkml]   [1999]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: fsync on large files

On Thu, 18 Feb 1999, Raul Miller wrote:

> On Thu, 18 Feb 1999, Raul Miller wrote:
> > > > > You might be able to get away with having a list of parents structure
> > > > > on multiply linked directories, which would have to be mirrored in
> > > > > dcache.
> Alexander Viro <> wrote:
> > And on rename() you will rebuild that data. How? Again, direct ancestors
> > may be even not in dcache yet when you do the first lookup.
> > What kind of data structure are you going to use?
> The list of immediate parents would have to exist on disk for every
> directory with more than one parent. I suppose I would base that data
> structure on the "indirect block" structure of a regular inode.

OK, so you are doing lookup on foo from /bar/baz. You see that foo is a
directory and it has another parent. You see that this parent is nowhere
near dcache/icache. Worse yet, actually it's the end of *long* chain of
directories and none of them (except the root, that is) is in dcache. To
make it even nastier, suppose that there are fan-ins in that chain (i.e
some of those directories also have multiple parents). Your actions?
Now, assume that another lookup goes through the alternative path in the
same time from the other direction. Your actions wrt locking?

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 13:50    [W:0.138 / U:2.892 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site