VFS Design

Discussions on more advanced topics such as monolithic vs micro-kernels, transactional memory models, and paging vs segmentation should go here. Use this forum to expand and improve the wiki!
Post Reply
Peterbjornx
Member
Member
Posts: 116
Joined: Thu May 06, 2010 4:34 am
Libera.chat IRC: peterbjornx
Location: Leiden, The Netherlands
Contact:

VFS Design

Post by Peterbjornx »

Heres the outline for the VFS rewrite of my OS, any remarks?

(pointers are arrows)
Image
User avatar
Combuster
Member
Member
Posts: 9301
Joined: Wed Oct 18, 2006 3:45 am
Libera.chat IRC: [com]buster
Location: On the balcony, where I can actually keep 1½m distance
Contact:

Re: VFS Design

Post by Combuster »

It's interesting that there's a separate list for files and subdirectories (and no symlinks, device files, ...), instead of a single list of "named children" with all the possible types as subclasses thereof. In essence, you have to make all the calling locations aware of all the types instead of trying to have them (mostly) oblivious to that.
"Certainly avoid yourself. He is a newbie and might not realize it. You'll hate his code deeply a few years down the road." - Sortie
[ My OS ] [ VDisk/SFS ]
embryo2
Member
Member
Posts: 397
Joined: Wed Jun 03, 2015 5:03 am

Re: VFS Design

Post by embryo2 »

Peterbjornx wrote:Heres the outline for the VFS rewrite of my OS, any remarks?
My remark is simple - I see it's a bit complex.

May be some short description can clarify your intent that made you to design this diagram?
My previous account (embryo) was accidentally deleted, so I have no chance but to use something new. But may be it was a good lesson about software reliability :)
Post Reply