memory management - How to conserve wastage of storage space in terms of # of blocks used when designing a file system -


as part of thesis, i'm working on designing storage sub-system. have create inode structure (like ext3 indirect block usage etc.). on same lines ext3 have 2 different page/block sizes - 16k , 512k (for direct block accesses). can have 36 blocks total. question how many blocks of each size should used minimize internal fragmentation or wasted storage space. suggested keeping 32, 16k blocks since 16k * 32 = 512k , avoid space wastage didn't follow argument much. please me understand logic.

the question ask first is: average file size encounter? lets average file size 256k...there can file size more 256k , less, average 256k. if so, keeping 1 512k block direct block causes internal fragmentation. having 16k blocks direct blocks covers files sizes <= 512k. so, reduce internal fragmentation, better size 16k.

now know this, there 2 questions ask you:

  • if go original unix design, why 8 direct block pointers used in inode? why trying use 32?
  • the second question ask is: why storage system support 16k , 512k block sizes?

i wait answer here :-)


Comments

Popular posts from this blog

c# - Send Image in Json : 400 Bad request -

jquery - Fancybox - apply a function to several elements -

An easy way to program an Android keyboard layout app -