/* Can inodes be fetched asynchronously? (Inode object is initially
* created in a pending state, and not unlocked until the data is actually
* available.) */
- int async_inode_fetches;
+ int sync_inode_fetches;
+
+ /* Should frontends handle requests serially or allow operations to proceed
+ * in parallel? */
+ int sync_frontends;
} BlueSkyOptions;
extern BlueSkyOptions bluesky_options;
* acquire locks on parents in the filesystem tree before children.
* (TODO: What about rename when we acquire locks in unrelated parts of the
* filesystem?)
+ * - An inode should not be locked while the filesystem lock is already held,
+ * since some code may do an inode lookup (which acquires the filesystem
+ * lock) while a different inode is locked.
* */
typedef struct {
GMutex *lock;
* set to the current time. If the inode is clean, it is set to zero. */
int64_t change_time;
+ /* Last access time to this inode, for controlling cache evictions. */
+ int64_t access_time;
+
/* Additional state for tracking cache writeback status. */
uint64_t change_pending; /* change_count version currently being committed to storage */
uint64_t inum);
void bluesky_directory_dump(BlueSkyInode *dir);
-void bluesky_block_touch(BlueSkyInode *inode, uint64_t i);
-void bluesky_block_fetch(BlueSkyFS *fs, BlueSkyBlock *block);
void bluesky_file_truncate(BlueSkyInode *inode, uint64_t size);
void bluesky_file_write(BlueSkyInode *inode, uint64_t offset,
const char *data, gint len);