About :: TODO :: Blog :: RSS :: Old blog :: Projects :: GIT :: Gallery :: Notes

Thu, 24 Jan 2008

POHMELFS development progress.

I've perfomed number of tests (before electricity was shut down), which included untar, execution and compilation of small objects, they all went perfectly fine except directory removal, it has some troubles because I only decrement number of links in object, not including directory itself, so funny things can be observed during unmounting (like 100% cpu usage produced likely by dentry cache processing code in VFS). I also found how crappy Debian Etch (or at least installation I have) is - I do not know why, but every ls operation tries first to access ldaprc file in every directory I ran it. If you would see which files gcc compiler wants to see in compilation directory for simple fstatat() testing application...

But overall it looks ok, so far without cache coherency protocol involved, but I think I have pretty clear idea on how to implement it correctly.

I'm looking at this and recall that not that long ago I wanted to get a linux kernel hacker position in some company, they developed multi-layer cache system (i.e. vanilla page cache in memory, then lower level cache on disk and finally tape storage) and asked me about my experience. It was quite miserable (and I would not say I suddenly became brilliant :). Then it was a question about what inode is...
And now I develop my own network filesystem, then local and distributed - how interesting things move with time, what will be next?... I belive that everything what happend was excellent, and will be even better.

/devel/fs :: Link / Comments ()