I think after realizing that Linux maintains 4 caches and we maintain 3 (of
I/O data), my main roadblock is the xfs_buf.h
Any input on it's working would be helpful. Meanwhile I'll proceed without
worrying about caching ATM.
Thanks,CruxBox
On Friday, 20 March, 2020, 2:00:22 pm IST, Shubham Bhagat
<dmarc-noreply@xxxxxxxxxxxxx> wrote:
Hi,
I recently hit a roadblock trying to implement XFS with read-only functionality.
While the specification for the file-system is available
(https://mirrors.edge.kernel.org/pub/linux/utils/fs/xfs/docs/xfs_filesystem_structure.pdf),
the only official source code available is in Linux.
While looking into implementing the B+Trees, I realized that to understand the
algos implemented, I'll need to understand linux buffer cache, page cache,
resource sharing / locking, filesystem VFS interfaces. I am not entirely sure
if it's the best approach.
The freebsd port for xfs (read-only) (now abandoned) didn't involve structures
from the specification: fxr.watson.org: OPENBSD sys/xfs/
The sooner I clear the roadblock, the more development we will see with xfs.
