Messages in this thread | | | Date | Mon, 29 Mar 2004 11:28:36 +0200 | From | Pavel Machek <> | Subject | Re: [PATCH] cowlinks v2 |
| |
Hi!
> > There are two possible implementations strategies for implementing > > cow files. You can either start as Jrn did with hardlinks, or you > > can start with symlinks. ... > There's a third implementation strategy. Since we're talking in all > cases about adding a new feature to the underlying filesystem, why not > implement separate inodes pointing to an underlying shared inode which > holds the data. (I think it was mentioned earlier in this thread).
Actually, there's 4th strategy, too. You could implement sharing at block level. Block free bitmap would become bigger, but you could do some tricks to keep it at ~8 bits per block... -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |