OSDev.org

The specification is at my site: http://www.angelfire.com/theforce/unspoken/

Any suggestions to optimize it?

Anyone?

Sir,
     Saw your file structure.  Inode structure used in MINIX (I don’t know about others). It some what resembles that(correct me if I am wrong).  what is the idea about the disk management and buffers?.  “C” , asm or C++ as language for those structs?.I am reading more to the spec.
    

ASM

Sir,
    Since disk device storage and cluster management uses extensive use of data structure.
As I was analysing FreeDos kernel source code file is implemented as a single link lists.
Buffer ,a structure represents a sector and with some algo it has been set to point to a valid buffer . I have also seen minix source code but I have not went deep in analysing in that.
But it is also uses the high level language  data structures and low level language for kernels.
     In your file system there is a use of next points. If it is going to be in asm what  asm ,
NASM or MASM etc. If you know the data structure in low level language please give me the link.
                  

THANX

NASM

OK, I updated the spec. Download the up-to-date file at http://www.angelfire.com/theforce/unspoken

Sir,
   I saw your file system again and I have suggestion (by giving this suggestion I am not going to be an advanced programmer. I am still learning things.).
    NASM is the assembler U are going for , is not it?. Try to read the documentation of NASM which explains about the assessing of structure (data) from / to C and ASM.
   Because of link list and data structures  is quit difficult in ASM.(for me).
Accessing  buffer in a “chain” ,as far as I know, is done by C at the backend.
Try to optimise with instruction and I give you link for optimising.

http://fatphil.org/x86/

And also go for Intel optimisation manuals.