Messages in this thread | | | Date | Sun, 16 Nov 1997 03:58:53 +0100 (MET) | From | Magnus Ahltorp <> | Subject | VFS |
| |
I am working on a filesystem that does not keep track of files using inode numbers, but rather using larger entities. Therefore, I have constructed a struct which keeps track of this entity, and stores this in u.generic_ip in my inodes. This is all well, but I have a problem. Linux's VFS is very inode number oriented. Since I have no real inodes, I have to construct these (for now, a counter++).
When I allocate an inode, I first call iget() with the fake inode number, and get an inode back. My read_inode() does nothing. I then fill the inode with the relevant information, just like read_inode would have done.
Is this way of handling things
1) Very ugly? 2) Harmful to cache algorithms? 3) Nonworking?
| |