file system block size
Hi All,
we want to write a new file system with block size more than
4KB. Can anyone suggest us how should we proceed ?
Regards,
Roushan
Quoted 3 lines · Roushan Ali
Hi All,
we want to write a new file system with block size more than
4KB. Can anyone suggest us how should we proceed ?
With great difficulty. ;)
There is really no support for this in the generic page cache code in the kernel, and you'd probably need some mechanism for doing multi-page metadata IOs. There's been sporadic discussion on fs-devel and linux-xfs in the past on this topic - you could search those archives for details.
cheers.
Signature · 1 line
Nathan
Quoted 6 lines · Nathan Scott
Quoted 3 lines · Roushan Ali
Hi All,
we want to write a new file system with block size more than
4KB. Can anyone suggest us how should we proceed ?With great difficulty. ;)
Indeed, it makes everything harder. Have a look at ntfs in the kernel which has to cope with file system block sizes between 512 bytes and several hundred kiB (at least they are in powers of two thank goodness...). You end up not being able to use a lot of generic functions as you for example need to lock multiple pages which needs to be ordered correctly, etc... If you look at the latest -mm kernel, the ntfs driver there has file write(2) support for any cluster size and you will see an example of the multiple page locking problem solution there.
Just one note is that I chose not to do full fs block size io in ntfs so I avoid most of the big problems. The only time it really hits is at allocation time, because you can only allocate in units of fs block size so when you write even one byte you need to lock the pages for the whole byte range from the fs block start to block end that includes the byte being written to. If already allocated, ntfs simply only writes to that one byte in the page it is in and ignores the other pages. Makes life much easier and faster given you save doing unnecessary writes to the other pages. (-: In fact we would only write out the 512-byte block containing the 1 written byte, so it is even faster than just page granularity. (-:
Best regards,
Anton
Signature · 4 lines
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
Quoted 8 lines
Indeed, it makes everything harder. Have a look at ntfs in the kernel which has to cope with file system block sizes between 512 bytes and several hundred kiB (at least they are in powers of two thank goodness...). You end up not being able to use a lot of generic functions as you for example need to lock multiple pages which needs to be ordered correctly, etc... If you look at the latest -mm kernel, the ntfs driver there has file write(2) support for any cluster size and you will see an example of the multiple page locking problem solution there.
Any chance this will make it into common code? I also need it for my filesystem driver (here: http://bobcopeland.com/karma/). So far I've only done read side which is not too bad, but as you say writing makes things complicated.
That, and the extent-supporting mpage_readpages would make me a happy person.
-Bob
Quoted 9 lines · Bob Copeland
Quoted 8 lines
Indeed, it makes everything harder. Have a look at ntfs in the kernel which has to cope with file system block sizes between 512 bytes and several hundred kiB (at least they are in powers of two thank goodness...). You end up not being able to use a lot of generic functions as you for example need to lock multiple pages which needs to be ordered correctly, etc... If you look at the latest -mm kernel, the ntfs driver there has file write(2) support for any cluster size and you will see an example of the multiple page locking problem solution there.
Quoted 6 lines
Any chance this will make it into common code? I also need it for my filesystem driver (here: http://bobcopeland.com/karma/). So far I've only done read side which is not too bad, but as you say writing makes things complicated.
That, and the extent-supporting
mpage_readpageswould make me a happy person.
Can you elaborate ? What would you like to see in mpage_readpages() ? Christoph recently posted patches to add support for getblocks() in mpage_readpages(). What else do you need ?
Thanks,
Badari
Quoted 6 lines · Badari Pulavarty
Quoted 1 line · Bob Copeland
That, and the extent-supporting
mpage_readpageswould make me a happy person.Can you elaborate ? What would you like to see in
mpage_readpages()? Christoph recently posted patches to add support forgetblocks()inmpage_readpages(). What else do you need ?
Yes, that is exactly what I was referring to. I think Christoph's patch will work great for my fs but I haven't had a chance to try it out yet.
-Bob