diff options
author | Andreas Baumann <abaumann@yahoo.com> | 2012-04-25 21:44:49 +0200 |
---|---|---|
committer | Andreas Baumann <abaumann@yahoo.com> | 2012-04-25 21:44:49 +0200 |
commit | 244cdd5d5a9641f494d0e1edb0737e167e5568f3 (patch) | |
tree | 9182d59f5a8b317e5aa4f2b2d0c7e8f956a78ace /DEVELOPERS | |
parent | ff33cf46862c7c88ae2250e787dd00f2b946c9e6 (diff) | |
download | pgfuse-244cdd5d5a9641f494d0e1edb0737e167e5568f3.tar.gz pgfuse-244cdd5d5a9641f494d0e1edb0737e167e5568f3.tar.bz2 |
updated some docu
Diffstat (limited to 'DEVELOPERS')
-rw-r--r-- | DEVELOPERS | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -29,6 +29,9 @@ Coding guidelines are simple enough. If possible avoid string manipulations as for timestamps (we are on low-level OS-abstraction layer, so 'struct timespec' and epochs are fine). + + Consistency of the data should be ensured in the database. + We don't want to implement an 'fsck' for pgfuse. Design desicions ---------------- @@ -77,6 +80,10 @@ How to tune the block sizes? What factors influence the experiment? At the moment we store padded blocks of fixes size (STANDARD_BLOCK_SIZE), not really sure if that is good or bad. +The block size should be computed (small files have only one block, +all other have a a blocksize of the first full block). Gets us more +independent on some configuration or options. + Directory tree in database -------------------------- |